The WebXR simulation window cannot be found in the debug window that appears after pressing F12 in the Edge browser.

[Simon1059770342]

The WebXR simulation window cannot be found in the debug window that appears after pressing F12 in the Edge browser.

[felixtrz]

I cannot repro on my side, and haven't heard from others about this issue. It might be at the very end of the list of tabs in the developer tools panel (could be retracted), and it won't show up if you are on browser reserved pages (for example edge://extensions/)

[sorskoot]

I had the same issue in Edge before. I switched to debugging on Chrome because of this issue. But today I noticed it in Chrome as well.

In this screenshot you can see that it is not in the list of hidden tabs. The polyfill is loaded. And, the extension is visible in the extensions bar at the top.

In the console there's only one message [Immersive Web Emulator] native WebXR API successfully overridden

[sorskoot]

Any news on this? It quite limiting in WebXR development at the moment, since I can only test and debug on a real device.

[mrdoob]

I cannot repro on my side, and haven't heard from others about this issue.

You did... I reported the issue some months before: https://github.com/meta-quest/immersive-web-emulator/issues/21

And I'm having the issue again.

[mrdoob]

Seems like Mozilla's extension is more reliable: https://chromewebstore.google.com/detail/webxr-api-emulator/mjddjgeghkdijejnciaefnkjmkafnnje

[felixtrz]

I cannot repro on my side, and haven't heard from others about this issue.

You did... I reported the issue some months before: #21

And I'm having the issue again.

I appreciate everyone's input on this issue. I want to clarify that since issue #21, we've completely rebuilt the Immersive Web Emulator's frontend in v1.3 using React. The issues here and the one reported by @mrdoob in #21 (followed up and closed after v1.3), while they manifested in a similar manner, are unlikely to be related due to these changes.

Despite our efforts, QA and I couldn't replicate the problem, suggesting it might be isolated. However, we've kept this issue open for further monitoring.

If you're experiencing this issue, please help by providing error logs from the Immersive Web Emulator section on chrome://extensions or edge://extensions. This information is crucial for our investigation. Thank you very much for your patience and assistance.

[mrdoob]

Where do we get the error logs from?

[mrdoob]

Can you try https://raw.githack.com/mrdoob/three.js/dev/editor/index.html?

Go to View/AR...

Then open devtools and see if the WebXR panel is there...

[felixtrz]

Where do we get the error logs from?

It should be here if there is any

[felixtrz]

Can you try https://raw.githack.com/mrdoob/three.js/dev/editor/index.html?

Go to View/AR...

Then open devtools and see if the WebXR panel is there...

I see it on both Edge & Chrome ...

[felixtrz]

The one possibility I can think of is if you have both Mozilla's extension and IWE installed at the same time, this can potentially cause a conflict since the tab name for both is "WebXR"

[felixtrz]

Did some more digging, and it seems that similar problems have been reported with a number of other devtools (React DevTool, Vue DevTool, etc.) that utilize the devtool tabs, most of these GitHub issues points to a few Chromium bugs:

• https://issues.chromium.org/issues/40218104 (stamped with a "fixed" but latest comments point to possible regression and the next bug)
• https://issues.chromium.org/issues/40070693 (seems to be still going on)

I will keep looking

[mrdoob]

Figured it out.

The extension doesn't show up when this checkbox is enabled:

[mrdoob]

I think Chrome devs are looking into it...