| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
| getDevice: function () { return {requestPresent: function () {}}; }, | ||
| isPresenting: function () { return true; }, | ||
| setDevice: function () {}, | ||
| setSession: function () { |
There was a problem hiding this comment.
can do one liner
Sorry, something went wrong.
There was a problem hiding this comment.
fixed
Sorry, something went wrong.
|
Thank you very much! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description:
As noted in #5217, and one reason that bug #5221 slipped through - the Enter / Exit VR tests for a-scene are still entirely focussed on WebVR rather than WebXR.
This PR adds some tests for WebXR
Changes proposed:
I approached this as follows;
I doubt this gives us perfect coverage of WebXR, but it should give good coverage of a broad range of key scenarios around entry to / exit from VR.
I have also confirmed that this set of tests would have caught the bug fixed under #5221.
Some very minor changes to a-scene also made, to allow simulation of WebXR availability via the el.hasWebXR flag.