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

Update to WebVR 1.1 #9

Open
spite opened this issue Sep 13, 2016 · 4 comments
Open

Update to WebVR 1.1 #9

spite opened this issue Sep 13, 2016 · 4 comments
Labels

Comments

@spite
Copy link
Owner

spite commented Sep 13, 2016

From the new spec, and this https://github.com/w3c/webvr/blob/gh-pages/js/webvr-1-1.js

@AVGP
Copy link
Contributor

AVGP commented Oct 20, 2016

So that needs VRFrameData and the corresponding methods, right?

@spite
Copy link
Owner Author

spite commented Oct 20, 2016

Yes, right now it relies on the page using a polyfill (https://toji.github.io/webvr-samples/js/third-party/webvr-polyfill.js).

The blockers right now are #10 and similar problems that were found while coding the webvr-recoder. Since some properties in VRDisplay are read-only, everything needs to be wrapped and it's a big rewrite. Same with Gamepad API.

Adding VRFrameData is trivial, I'm just holding on to the spec changes while preparing the wrapper rewrite.

@AVGP
Copy link
Contributor

AVGP commented Oct 20, 2016

Oh right, I see.
Just FYI: WebVR 1.1 has landed in Boris' polyfill directly: https://github.com/googlevr/webvr-polyfill/pull/149/files

So, yeah, let me know what I can do right now to help ya out! 👋

@spite
Copy link
Owner Author

spite commented Nov 10, 2016

VRFrameData and VRDisplay.getFrameData implemented in 100da95

Seems to work ok, but there's some weird issue with webvr.info/samples and Canary at the moment. All other content in Stable seems to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants