Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move API methods and events to navigator.vr namespace #152

Closed
cvan opened this issue Nov 15, 2016 · 1 comment
Closed

Move API methods and events to navigator.vr namespace #152

cvan opened this issue Nov 15, 2016 · 1 comment
Milestone

Comments

@cvan
Copy link
Contributor

cvan commented Nov 15, 2016

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.

@toji
Copy link
Member

toji commented Feb 6, 2017

Closing now that #116 is merged.

@toji toji closed this as completed Feb 6, 2017
@cwilso cwilso modified the milestones: Spec-Complete for 1.0, 1.0 Apr 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants