Intent to Continue Experimenting: Web XR Device API
Chris Wilson
Contact emails
baj...@chromium.org, cwi...@chromium.org, eri...@chromium.org
Spec
-WebXR : https://immersive-web.github.io/webxr/spec/latest/ (explainer)
Summary
An Origin Trial for WebXR was originally launched in Chrome 67. From that experiment we learned that there was not much developer interest until we could provide comparable feature capability for WebVR, most notably around Input (see public discussion -> https://github.com/immersive-web/proposals/issues/17).
As the spec continued to evolve (main changes tracked here), we wanted to provide another chance via origin trial for developers to try out the new API shape, and we did so in 70-71; unfortunately, we did not get the message out well enough to the community outside blink-dev that the WebVR OT was expiring, and it’s only now (literally today, 11/29) that one of our test partners (the Google Poly Tour Creator team) is deploying their WebXR-based implementation to test it out.
Link to “Intent to Implement” blink-dev discussion
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/XMLgC_SR0dw
Goals for experimentation
We are continuing to seek input on WebXR Device API ergonomics, now that WebVR is no longer supported. As previously noted, our specific partner here is the Tour Creator team. As we’ve been assisting them with their WebVR->WebXR conversion, this has turned up some challenges for them already (headset insertion instructions not showing on Cardboard, lack of device IDs) that we’re using to push goals in the spec.
Experimental timeline
Enabled : Chrome 72 (extended from 70-71)
29 NOV 2018 : Chrome 72 branch to Dev
29 JAN 2019 : Chrome 72 Stable*
Disabled :
24 JAN 2019 : Chrome 73 branch to Dev
12 MAR 2019 : Chrome 73 Stable*
*Stable dates are estimates: https://www.chromium.org/developers/calendar.
Any risks when the experiment finishes?
We expect to file another Intent to Experiment for WebXR support in M73/74, with breaking changes that are being designed in the WebXR API today. With that separate OT, sites can migrate to a closer-to-shipping version of WebXR.
Reason this experiment is being extended
As mentioned previously, we would like to extend the trial due to the ship cycles of our partner. This feedback would then be included in subsequent experiments/trials, and we expect to file a new Intent to Experiment with breaking changes in the Web XR device API.
Also, note that we intend to let the Gamepad Extensions for WebXR origin trial expire with M71; we’ve concluded it’s not necessary in the short term, and substantially far from the design we hope to eventually ship (which we will be filing to experiment with in several milestones).
Ongoing technical constraints
none
Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?
The WebXR trial will include both Android & Windows platforms. We do intend to evaluate support on any platforms that gain VR hardware support in the future.
Link to entry on the feature dashboard
OWP launch tracking bug : https://crbug.com/864810
Intent : https://www.chromestatus.com/feature/5680169905815552 (WebXR)
Chris Harrelson
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAByQ9nvBWgiF77g%3DpQe4Q4dHJKf7ubW%2ByrgpwhcWOVNdVocx6Q%40mail.gmail.com.