Summary: The successor to WebVR 1.1, the WebXR Device API 1.0, is nearing finalization. The WebXR Device API follows modern Web API patterns, is extensible additively for augmented reality, enables use within Web Workers, and solves many security problems for the VR and AR enabled web. The spec has been developed jointly by implementers from all major browser vendors, within the W3C Immersive Web Community Group. A full W3C Working Group is now being formed, with a charter and assigned chairs.
As of 2019-10-01 I intend to turn the WebXR Device API 1.0 on by default in Nightly for on all platforms that already support WebVR (Windows, Linux, macOS, and Firefox Reality / GeckoView). Chrome 67 Beta has shipped WebXR as an Origin Trial. Bug to implement: Bug 1419190 - [meta] Implement WebXR 1.0 https://bugzilla.mozilla.org/show_bug.cgi?id=1419190 <https://bugzilla.mozilla.org/show_bug.cgi?id=1419190> Bug to turn on by default in Nightly: Bug 1479617 - Enable WebXR 1.0 by default in Nightly https://bugzilla.mozilla.org/show_bug.cgi?id=1479617 <https://bugzilla.mozilla.org/show_bug.cgi?id=1479617> Link to standard: The api is documented on the immersive-web GitHub page: https://immersive-web.github.io/webxr/ <https://immersive-web.github.io/webxr/> The “API Explainer” is a good place to start for newcomers to the WebXR Device API: https://github.com/immersive-web/webxr/blob/master/explainer.md <https://github.com/immersive-web/webxr/blob/master/explainer.md> Platform coverage: WebXR will be supported everywhere that WebVR is currently. This includes Windows, Linux, macOS, and Android/GeckoView (Firefox Reality). Estimated or target release: The implementation is expected to be completed for Firefox 73, but would be enabled as early as Firefox 71 if implementation goes quickly. Preference behind which this will be implemented: The dom.xr.enabled pref will enable the WebXR Device API. Initially, this will be flipped for Nightly only. Once final TAG review feedback has been completed, any late breaking changes will be implemented before enabling in Release. A separate "intent to ship in release” will be sent to announce this. Flipping the dom.xr.enabled pref will not disable the existing WebVR api. We wish to keep WebVR enabled for a grace period until most popular engines and sites (eg, threejs and aframe) have migrated to WebXR. An “intent to unship WebVR” will be sent with details of this deprecation once WebXR is in release. Is this feature enabled by default in sandboxed iframes? WebXR will not be enabled by default in sandboxed iframes. This will likely be enabled later, by use of Feature Policy: https://github.com/immersive-web/webxr/issues/86 <https://github.com/immersive-web/webxr/issues/86> Do other browser engines implement this? Chrome has implemented this with an origin trial expected to start in Chrome 67, for both desktop and Android. https://www.chromestatus.com/feature/5680169905815552 <https://www.chromestatus.com/feature/5680169905815552> web-platform-tests: Additional web-platform-tests for WebXR will be added during our implementation and submitted to the repo: https://github.com/web-platform-tests/wpt/tree/master/webxr <https://github.com/web-platform-tests/wpt/tree/master/webxr> A meta bug has been created to track the needed tests as they are identified: Bug 1479626 - [meta] Implement web-platform-tests for WebXR https://bugzilla.mozilla.org/show_bug.cgi?id=1479626 <https://bugzilla.mozilla.org/show_bug.cgi?id=1479626> Is this feature restricted to secure contexts? Yes. All implementers in the W3C CG have agreed to enable only in secure contexts. How stable is the spec: Final TAG review and W3C Working Group discussion may result in late breaking changes. These changes are expected to affect the syntax of the API and not the general behaviour. Any changes are expected to be identified before our implementation is ready to ship to release. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
