Automatic update from web-platform-tests
Update WebXR TestAPI and tests to match new spec (#17630)
Now that WebXR is more mature, the test API is being revisited with
input from other UAs. This change updates existing methods and tests
to match the new API, which largely involves:
* FakeXRDeviceInit now requires views
* FakeXRDeviceInit *CAN* support an initial viewerOrigin
* setXRPresentationFrameData is now setViews and set/clearViewerOrigin
* XRTest is now navigator.xr.test [1]
As part of this, webxr_test_constants were cleaned up and expanded to
help minimize boilerplate code in the tests. Where possible tests that
were previously calling setXRPresentationFrameData to ensure that the
fake device was "tracking" were updated to instead use a constant that
sets these values. Future work (after the API update is complete) will
identify if there are any cases where an initial requestAnimationFrame
could be removed.
Most changes (especially to vr/ tests) should be fairly mechanical, but
now that the eye offsets expected/set by the test are actually being
plumbed through, both xr/xrReferenceSpace_originOffset tests had to have
their expected matrices updated. Two tests had to be updated due to the
discovery of 981003.
Other changes to update to the Test API after this change should be
mostly additive and should actually already exist in the internal tests.
[1] XRTest currently still exists as a workaround until 944987 is merged
Also due to the fact that accessing xr blocks VR, the WebVR tests had to
be updated to set a special flag to tell the test API to not set the
object on XR. It's unlikely that this behavior will be able to be
removed after 944987, but to allow XRTest to be removed these tests have
had it migrated to navigator.vr.test
Bug:979312
Change-Id: I19ccffd921728ec3799252693d945b7b3f99d757
--
wpt-commits: 3f8ee365a7cacc091dc1dd1d0b5f21a89241c894
wpt-pr: 17630
An explanation of the Mozilla Source Code Directory Structure and links to
project pages with documentation can be found at:
https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure
For information on how to build Mozilla from the source code, see:
https://developer.mozilla.org/en/docs/Build_Documentation
To have your bug fix / feature added to Mozilla, you should create a patch and
submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at:
https://developer.mozilla.org/en/docs/Creating_a_patch
https://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree
If you have a question about developing Mozilla, and can't find the solution
on https://developer.mozilla.org, you can try asking your question in a
mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups
are accessible on Google Groups, or news.mozilla.org with a NNTP reader.]
Nightly development builds can be downloaded from:
https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/
- or -
https://www.mozilla.org/firefox/channel/desktop/#nightly
Keep in mind that nightly builds, which are used by Mozilla developers for
testing, may be buggy.
d8823a497f