Contact emails
baj...@chromium.org, meganl...@chromium.org, eri...@chromium.org
Spec
-WebVR 1.1 : https://immersive-web.github.io/webvr/spec/1.1/, being replaced in M66 with
-WebXR (formerly WebVR 2.0) : https://immersive-web.github.io/webxr/spec/latest/ (explainer)
Summary
An Origin Trial for WebVR was originally launched in Chrome 56, and renewed for M59-M61 (and again for M62-64) with changes based on feedback and the long term spec direction. The results of that experiment to date have been reported and we feel it's been a productive experience that has proven popular with developers.
With the forthcoming larger scale changes, and a plan to help migrate current users of this API to the new API (for which we will conduct a new trial), we would like to get feedback on the migration over the M66-67 timeframe. The purpose of this extension is to provide that time (M66-67) for developers to migrate from WebVR 1.1 to WebXR (formerly WebVR 2.0) while the trials for both overlap.
Link to “Intent to Implement” blink-dev discussion
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/m32Yy87Ggt0
Goals for experimentation
While we are not intending on changing the existing WebVR API (which we would like to extend trial for), we are wanting to extend the trial so as to provide a 2 milestone overlap where developers can migrate from WebVR 1.1 to WebXR Devices API.
Experimental timeline
Enabled :
18 JAN 2018 : Chrome 65 branch to Dev
23 JAN 2018 : Chrome 64 Stable*
1 MAR 2018 : Chrome 66 branch to Dev
6 MAR 2018 : Chrome 65 Stable*
12 APR 2018 : Chrome 67 branch to Dev
17 APR 2018 : Chrome 66 Stable*
29 MAY 2018 : Chrome 67 Stable*
Disabled :
24 MAY 2018 : Chrome 68 branch to Dev
24 JUL 2018 : Chrome 68 Stable*
*Stable dates are estimates: https://www.chromium.org/developers/calendar.
Any risks when the experiment finishes?
Unless the API transitions to stable, sites will lose the ability to interact with VR hardware. Given that hardware availability is limited we are encouraging developers to write responsive content that can account for its absence, but anything that relies on VR features would stop working.
Reason this experiment is being extended
As mentioned previously, we would like to extend the trial to allow us to get feedback on migration from existing WebVR 1.1 to WebXR (planned to overlap in the Chrome 66-67 timeframe).
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)?
Yes - the WebVR API will be available on all platforms. Moving forward, 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/670502
Intent :https://www.chromestatus.com/feature/4532810371039232 (WebVR)
https://www.chromestatus.com/feature/5680169905815552 (WebXR)Eric Deily | | Tech Prog Manager | | eri...@google.com | | +1 425-269-0869 |
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/66cd0db7-8b9e-41e1-be18-39dcd66226bb%40chromium.org.
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/cd9bef6b-c298-4b5b-8530-f1bd29230da6%40chromium.org.