First things first, congratulations on getting this close!
What's the status of the specification? I just had a quick skim and it seems extremely light on details.
There is quite a bit of details missing. The security model is essentially blank, and the descriptions in section 4 seem to be high-level overviews of what the DOM interfaces do, rather that detailed descriptions that can be used in order to implement the specification.
Also some things that I was expecting to see in the API seem to be missing. For example, what should happen if the VR device is disconnected as the application is running? It seems like right now the application can't even tell that happened.
Another question: do you know if Chrome is planning to ship this feature at some point? Has there been interoperability tests?
Do we know what the other browser vendors think of the API and the specification?
Thanks, Ehsan On 2015-10-26 3:19 PM, Kearwood "Kip" Gilbert wrote:
As of Oct 29, 2015 I intend to turn WebVR on by default for all platforms. It has been developed behind the dom.vr.enabled preference. A compatible API has been implemented (but not yet shipped) in Chromium and Blink. Bug to turn on by default: https://bugzilla.mozilla.org/show_bug.cgi?id=1218482 Link to standard: https://mozvr.github.io/webvr-spec/webvr.html _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
