I’ve got a conundrum. We do not have WebXR support in standard desktop or mobile builds of Firefox. It is, however, available in Firefox Reality. But we don’t have an entry for that in BCD, and I don’t think it is in a position to warrant having one.
So how do I indicate that there are in fact ways to experiment with WebXR? Right now, the compat tables are all “no” across the board, but that’s not an entirely accurate portrayal of reality. It’s available in Chrome Canary builds if you enable it with flags, and there’s Firefox Reality of course.
@jmedley: What do you guys at Google think in terms of how or if to express the ability to experiment with WebXR in Chrome? I know as a rule you guys more or less don’t like to list something as supported until it’s actually shipped.
I’m torn on what my personal preference is here. I don’t feel like the API is stable enough to want to go and try to maintain compatibility specifics for every subfeature right now. Maybe we could add notes to the interface/dictionary level saying something like “Although unsupported in Firefox desktop and mobile, the
XRFoo interface is available in Firefox Reality.” Might not be necessary at this point to go into further detail than that.
Thoughts? Other ideas? Probably would be helpful to get an opinion from @Elchi3.