Rik Cabanier
Rik Cabanier
We discussed this in today's WG meeting but I didn't feel like we got closer to a consensus. To clarify, these are the features that I believe the API should...
> > In a headset session, it's possible that this means only recording from one layer. > > Headsets are the only devices that implement layers at this point, but...
> > The API should NOT: > > > > * present a UA drawn configuration dialog box. > > should be an explicit requirement. (Unless you meant mandate instead...
The WebXR spec already allows this. Please search for "Magic Window" in the repo.
@simultech and I discussed this and we suspect that no additional API is needed to enable this. While in non-immersive mode, if an element gets focused, we bring up the...
I can't make any promises but if we can get it to work, we'll likely have a setting under chrome://flags so people can experiment.
> The biggest issue I see right now is the interoperation between immersive session and this keyboard. Mainly 2 specific ones > > 1. Occlusion with controller and other stuff...
We are making progress on enabling the native keyboard during an immersive session. As mentioned before, it will be triggered by focusing an element just like on a 2D page....
@HyroVitalyProtago What would be the usage of this metadata? Is it strictly for indexing or do you have other cases in mind?
@brianpeiris thanks! it would indeed be nice if there was a way to query for immersive content. @toji , do you know of any efforts to make page report their...