search

immersive-web / webxr-polyfill

Use the WebXR Device API today, providing fallbacks to native WebVR 1.1 and Cardboard
Apache License 2.0
386 stars 86 forks source link

WebXR 2019 #51

Closed jsantell closed 4 years ago

jsantell commented 5 years ago

This is a meta bug for discussion around updating the polyfill to the latest version of the spec now that things have settled down a bit.

I've created a handful of categorized issues, detailing what I'm aware of that has changed at least, and areas that probably need to be confirmed. The issues are all tagged in the WebXR 2019 milestone.

Contributing/development

If you're interested in contributing, express interest in an issue! We will be using the webxr-2019 branch for PRs. There are examples (originally from webxr-samples) in the repo that we can use to test progress as we iterate inbetween two APIs, hopefully ending up with something functionally similar to what could be on webxr samples in the future.

The polyfill has two main areas: the API plumbing (src/api/*) and providers (src/devices/*. Not only will the API have to be updated to match the spec, but the input between the API and the underlying provider may also need to change.

We can test against WebVR and non-WebVR mobile browsers using the WebVRDevice provider and CardboardXRDevice provider. If we can incrementally make these changes while updating the local examples, then we should still be able to support the examples in these browsers as a means of testing. In addition to the traditional unit tests here to help with the plumbing.

Happy to answer any questions about the structure of the current code!

cwilso commented 5 years ago

I added the agenda label because I want to make sure we discuss the polyfill and its trajectory in the next WG call.

jsantell commented 4 years ago

The migration to the current WebXR standard has been completed.