Unable to access 3D view

[crrobinson14]

While using Edge to debug a Teams Tab App (as started automatically by the Teams Toolkit from VSCode) on a Mac (M1) I receive the following error. But there appears to be no way to identify or install whatever components are "missing". I am definitely connected to the Internet.

AB#46958989

[captainbrosset]

Oh that's weird. Thanks so much for filing this. I will make sure this is being tracked by the dev team.
In the meantime, have you tried closing and re-opening DevTools and see if that forced the downloading of the missing component? Also, is there an info banner appearing just above DevTools about this?

[captainbrosset]

I just had the same problem, on Windows 11. Re-starting DevTools got rid of the message. However the DOM and z-index tabs didn't work like they should. Only the Composited layers tab worked. Are you seeing the same problem?

[crrobinson14]

@captainbrosset Restarting DevTools doesn't seem to resolve it for me (by which I assume you mean the reset/restart button in DevTools prefs). But I have the same experience you do where Composited Layers does appear to have some entries in it:

Happy to test anything else you like since I can reproduce this 100%.

[captainbrosset]

Thanks @crrobinson14 for the detail. Our team is looking into this. We'll let you know of any questions we have and when we have a fix coming.

[mtbayley]

I have also been running into this for several months now

[captainbrosset]

For information, we have 2 fixes on the way for this:

1. The message will be made a bit clearer. The 3D view is a component that's not built-in to Edge. It's only downloaded on-demand, the first time you use the 3D view. So you do have to close and re-open DevTools the first time, for it to work. The first fix is about making the message more clearly explain this.
2. The DOM and z-index tabs appear frozen, only the Composited Layers tab works at the moment. We have this bug tracked as well, and are working on a fix for this regression.

Thanks for your patience!

[vidorteg]

Hi everyone, Edge Devtools Developer here,

We put out a couple of fixes for the issues mentioned in here:

1. The message is shown whenever some of the Devtools components need to be updated/reloaded. We modified the message to make it more clear including steps on how to fix it.
2. We fixed the issue and Z-Index and DOM should be working again.

both fixes should make its way to Edge Canary soon and then to the rest of the channels, thank you for the report.

[huebnerr]

Thank you very much. I'm attempting to debug a Z-indexing issue and was confused why the other Z-index and DOM seemed to be frozen.

[captainbrosset]

Thank you very much. I'm attempting to debug a Z-indexing issue and was confused why the other Z-index and DOM seemed to be frozen.

Do the z-index and DOM tab work for you now? They used to be broken before, but this bug should now be gone. Let us know if you still have an issue.

[vanowm]

This issue is not resolved on Windows.
When Edge is launched from VSCode debugger, 3D View is not available.

Here is a command line used to launch Edge:

"C:\Users\Dev\AppData\Local\Microsoft\Edge SxS\Application\msedge.exe" --disable-background-networking --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-default-apps --disable-dev-shm-usage --disable-renderer-backgrounding --disable-sync --metrics-recording-only --no-first-run --no-default-browser-check "--user-data-dir=e:\Program Files\VSCode\data\user-data\User\workspaceStorage\f8081997708878520f20c6fb314afe8f\ms-vscode.js-debug\.profile" --auto-open-devtools-for-tabs about:blank --remote-debugging-pipe

The issue here is --disable-default-apps flag. If Edge was launched with this flag just once, there is something left in the profile which prevents 3D View to initialize even after edge was launched without that flag.
The only way to bring 3D View back is to launch Edge without --disable-default-apps and --disable-background-networking flags. After that, we can add back --disable-background-networking flag and '3D View` will still work.

[captainbrosset]

Thanks for posting. I moved this to a new issue since it might be a different problem, and since this issue is now closed.

[NkmGlobal]

Thanks for posting. I moved this to a new issue since it might be a different problem, and since this issue is now closed.

Im facing this same challenge. Any update on fixes?

Thank you very much. I'm attempting to debug a Z-indexing issue and was confused why the other Z-index and DOM seemed to be frozen.

Do the z-index and DOM tab work for you now? They used to be broken before, but this bug should now be gone. Let us know if you still have an issue.

[captainbrosset]

No, unfortunately no update on that specific issue. If you have new information to share about it, could you please provide it in issue #212? The more information we have to reproduce and debug the problem, the better. Thank you.