Manish Goregaokar

We already have a lot of fingerprinting concerns about `isSessionSupported()`, I'm a bit wary of enabling it to expose further details about the system. Some of this could be managed...

There may be an approach here that instead gets implementors to estimate the real hit-tested floor whenever possible; this has been discussed a bit amongst implementors.

What do you mean by keyboard-only interactions? If you have a bluetooth keyboard connected to the device it will work as usual, the only issue is that XR content currently...

> FWIW keyboard input currently doesn't work while in immersive mode on the Oculus browser. Oh yeah because there's nothing to type into. That's fair. > Did we define where...

Anyway, I think the main thing is that because there is no accessibility tree possible for webgl content, keyboard-only interactions don't really _exist_ for webxr. This issue is about eventually...

@RealJoshue108 I'm well aware: what does this have to do with native _virtual_ keyboards? If anything the virtual keyboards on XR devices are _less_ accessible: there is no tactile feedback...

> I agree that's likely out of scope for the first version of WebXR but we should have support later. It's feature that several people have requested. Absolutely, that's what...

Right, he's saying that the application should be fixing this by offsetting to the initial viewer pose (and the framework can do this for you if possible). That said, defining...

> Let's say an end user goes immersive and decorates their room with furniture. local spaces shouldn't be used for this tbh. But this is a super valid concern, yeah,...

Servo on Hololens uses OpenXR, and I believe the OpenXR runtime sets LOCAL spaces to the head position at session start.