Last I looked, we didn't have any tests for VRFrameData, FWIW (bug 1317258). I see some now under servo/ but presumably we don't run those. Maybe I'm missing some.
It would also be good to make sure our internal fuzzers are fuzzing these APIs to at least catch basic errors. Andrew On Wed, Mar 1, 2017 at 1:32 PM, Boris Zbarsky <bzbar...@mit.edu> wrote: > On 3/1/17 3:50 PM, kgilb...@mozilla.com wrote: > >> As of March 1, 2017 I intend to turn WebVR on by default on Windows. >> > > So flip the pref on Windows only, right? > > If there is no VR hardware, is the idea that navigator.getVRDisplays() > returns a promise resolving to an empty array? > > Link to standard: https://w3c.github.io/webvr/archive/prerelease/1.1/ >> > > It's a bit worrying to me that this spec is not written down in sufficient > detail to be implemented interoperably [1]. How confident are we that what > the other browsers are shipping matches what we're shipping? Are there web > platform tests? > > -Boris > > [1] For example, what does the VRFrameData constructor actually do? The > spec doesn't define it at all. Where is the VRPose inside supposed to come > from? What values will it contain? I filed > https://github.com/w3c/webvr/issues/195 on this, but note that I've spent > all of about 5 minutes skimming the spec and ran into this. I have _not_ > done a careful read looking for possible interop problems... > > _______________________________________________ > 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
