Closed takahirox closed 2 months ago
I found this section
- Conformance Interfaces and functionality exposed by this specification SHOULD NOT be exposed to typical browsing experiences, and instead SHOULD only be used when running Web Platform Tests.
So it seems WebXR testing API shouldn't be enabled as default...
A solution idea is suggesting to add WebXR Testing API
to permissions of manifest.json which allows the extension to access WebXR Testing API.
Opened an issue to ask if WebXR Testing can be exposed to browser extension https://github.com/immersive-web/webxr-test-api/issues/48
From https://github.com/MozillaReality/WebXR-emulator-extension/issues/34#issuecomment-581634334
It may be good to rewrite the current
EmulatedXRDevice
to the one with WebXR testing API. Benefit is the emulator can even work with the native WebXR API, we will no longer need to override the native API with the polyfill. One concern is whether WebXR Testing API is enabled as default or not. I don't think it's good for browser extension to rely on a feature behind a pref.