Don't miss out on the action at this year's Chrome Dev Summit, streaming live on YouTube. Watch now.

WebVR changes in Chrome 62

The current WebVR origin trial is ending on November 14, 2017, shortly after the stable release of Chrome 62. We have begun a new trial with the WebVR 1.1 API in Chrome 62 that will continue through Chrome 64.

The new trial includes some API behavior updates that are consistent with the direction of the forthcoming WebVR 2.0 spec:

  • Use of WebVR is restricted in cross-origin iframes. If you intend for embedded cross-origin iframes to be able to use WebVR, add the attribute allow="vr" to the iframe tag, or use a Feature-Policy header (spec discussion, bug).
  • Limit use of getFrameData() and submitFrame() to VRDisplay.requestAnimationFrame() (spec discussion, bug).
  • window.requestAnimationFrame() does not fire if the page is not visible, meaning it will not fire on Android while WebVR is presenting (spec discussion, bug).
  • The synthetic click event at viewport (0, 0) has been removed (for both Cardboard and the Daydream controller touchpad) (bug). The vrdisplayactivate event is now considered a user gesture, and may be used to request presentation and begin media playback, without relying on the click event. Code that was previously relying on click event handlers for input should be converted to check for gamepad button presses. (Example implementation)
  • Chrome may exit presentation if the page takes greater than 5 seconds to display the first frame (code change). It is recommended that the page display within two seconds and that a splash screen is used if needed.

Your current WebVR Origin Trial tokens will not be recognized by Chrome 62. To participate in this new trial please use the sign up form.