You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on conversations and PR #116 opened by @toji, for v1.2, we intend on moving the current VR interfaces under the navigator.vr namespace and emit events on the VRDisplay instances instead of on window. This is a required change to enable folks to use WebVR in a worker context (where the DOM is inaccessible).
Luckily, although this is a backwards-incompatible change, these new interfaces and events can be easily polyfilled so existing WebVR sites using the current (v1.1) API can drop in a polyfill and use the new interfaces.
It's an implementation matter, but User Agents that have implemented the existing (v1.1) WebVR API interfaces and events should continue to support the old API and events but provide Console warnings to web developers, if possible.
The text was updated successfully, but these errors were encountered:
Based on conversations and PR #116 opened by @toji, for v1.2, we intend on moving the current VR interfaces under the
navigator.vr
namespace and emit events on theVRDisplay
instances instead of onwindow
. This is a required change to enable folks to use WebVR in a worker context (where the DOM is inaccessible).Luckily, although this is a backwards-incompatible change, these new interfaces and events can be easily polyfilled so existing WebVR sites using the current (v1.1) API can drop in a polyfill and use the new interfaces.
It's an implementation matter, but User Agents that have implemented the existing (v1.1) WebVR API interfaces and events should continue to support the old API and events but provide Console warnings to web developers, if possible.
The text was updated successfully, but these errors were encountered: