-
Notifications
You must be signed in to change notification settings - Fork 370
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
[CLOSED] Changed requestPresent to accept a sequence of VRLayers #36
Comments
Comment by toji If this change were to go into effect I would probably keep the non-array variant of the function in Chrome's experimental builds for a bit and have them print a deprecation warning to the console when used, just so any 1.0 compatible content people have built doesn't immediately fail. |
Comment by cvan needs rebase |
Comment by cvan this looks great. r+ and that's no joke 👍 |
Comment by mkeblx Saw this in IDL. |
Comment by cvan oh, good catch. gotta fix that. |
Issue by toji
Thursday Mar 31, 2016 at 17:29 GMT
Originally opened as MozillaReality/webvr-spec#28
Also added
maxLayers
capability. As per conversations with @vvuk. Still restricts the v1 spec to only accepting a single layer, but makes future changes to allows for more complex compositing more sensible.toji included the following code: https://github.com/MozVR/webvr-spec/pull/28/commits
The text was updated successfully, but these errors were encountered: