There is still a set of tests that have not been moved over:
XRWebGLLayer tests
src/third_party/WebKit/LayoutTests/xr/xrView_match.html
There is also a selection of tests that can't be easily moved over for various reasons:
Tests testing things not formally defined in the spec:
AR related tests.
Tests for XR and VR not running at the same time.
Tests for detached subframes.
Tests for gamepad input
exclusive_requestFrame_nolayer.html
xrpresent canvas context
timestamp
depthNear/depthFar
Tests for things not supported by the test spec:
XRInput events
stage FrameOfReference tests
environmentBlendMode
Tests that have incompatibility issues:
src/third_party/WebKit/LayoutTests/xr/events_deviceconnect.html
This test needs to have a deplay before simulateDeviceConnection. This is due to the fact that the mocking needs to let the mojo calls go through and set up the listeners before calling the change event. We currently handle this with a setTimeout in the test, which is bad and should not be uploaded. What we should have is a runLoopUntilIdle function in the chromium specific mocking.
src/third_party/WebKit/LayoutTests/xr/events_session_resetpose.html
The way we handle reset pose means that in order to get the event you have to request an animation frame. That is not part of the spec, and so the test is not trasferable. If we rewrote it to be inline with the spec, it would not pass in chrome. http://crbug.com/843184
src/third_party/WebKit/LayoutTests/xr/xrViewport_valid.html
This partially tests spec defined functions, and partically not. webglLayer.getViewport is defined, but the test makes some assumptions about there being a left and right viewport, which is not defined by the spec. This test will need to be broken into two, or a new test written which tests only the spec defined behaviour.
Comment 1 by offenwanger@chromium.org
, Jul 20