Closed jfcampos closed 6 years ago
The shim in webxr-samples handles the conversion from non-latest WebXR spec usage to whatever the latest is, e.g. converting exclusive
to immersive
on older builds of Chromium, I think this will solve the issue. Is that sufficient?
Also, I did not know that Oculus Go has a WebXR implementation; if so, which Chromium version is it similar to?
Thanks, that's helpful.
Go uses v61 and does not suppot webxr natively. I was having the non supported error (using the polyfill) and I didn't know whether or not exclusive/immersive was part of webvr as well. But guess what, it does work now with immersive, I think it was a cache issue...
Sounds good! The spec is going through a lot of changes still so this polyfill will attempt to track the latest, so there will be some growing pains for a bit more.
It seems that session type "immersive" instead of "exclusive" is not supported yet in oculus browser (Oculus Go). Is it possible to support both terms until the transition is done in all browsers?
This works: