-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable foregrounding of 2D browser #1316
Comments
/agenda |
It does make sense - you should be able to watch TV, so a web page isn't much different. However... What happens if the "2D browser" wants to show 3D content? Might there be any leak of data from one site to another? |
Rik's description is that the browser window is a modal "window" - it requires dismissal before the WebXR session can accept new input. |
Rik states that this is to open the web page that launched the WebXR session.
|
WebXR is always launched from a browser. I don't know any workflow where that is not the case.
It must the browser that is running the current WebXR session
Yes. It should have the same capabilities as the regular 2D site
I don't believe it should act differently from a regular WebXr session. A navigation will close current session and go back to the 2D environment.
Nothing
This was mentioned during the discussion. I think the browser should show with no navigation or URL bar.
It would be up the the UA to decide but in the case of Quest it would be world locked. |
My 2 cents based on the impressions from today's call: it sounds like a spin on DOM layers, so maybe we should tackle it by standardizing those? Similarities I see:
Given that it's the app that is controlling the displayed content, we probably would want to avoid entering visible-blurred state if possible (i.e. when there's no 3rd party content rendered, or maybe blur only when the user is interacting with 3rd party content?) - otherwise, it wouldn't be that much different from using the OS to multitask by bringing up a 2d browser into the immersive session. In general, it feels a bit like we'd face the same challenges as the ones we would have to solve for DOM layers (handling input, handling 3rd party content, tackling privacy + security issues w/ no trusted pixels) that it may not make sense to make this distinct from adding a DOM layer. |
My intent is to bring up the 2d browser as if it's done by the OS. |
And would bringing up the 2D browser then allow navigation (I'd guess not as that would cause the session to unload)? Or switching tabs? It seems very much like trying to fill a role that the OS should likely fill/provide; though given that the browser is technically active for the WebXR session, it may not be selectable via those usual mechanisms? I do think we need to tread very carefully here from a privacy/security perspective; so I don't think limiting the browser's appearance is really overthinking that much, and if we're limiting the appearance, are there things that we feel that the full browser would allow (or we could allow from a privacy/security perspective) that would be that different from what DOM Layers could allow? |
My point is that if it's still the browser (as opposed to the OS) doing the actual work of displaying itself inside an immersive session, it seems to me that roughly the same work would be needed to correctly implement DOM layers and the same problems would need to be solved, so maybe we should go with that approach? 😄 |
Navigation is always allowed; even during an WebXR session.
Again, it would be to minimize confusion.
With DOM Layers, the XR session continues to get controller or hand input when the user interacts with the layer. Because of this, we decided that only same origin content would be allowed there. The other thing that is hard about layers is that each layer would be its own window with its own state which is much harder than just showing the existing window in regular state. |
Issue #1365 is a duplicate of this. |
How useful would it be to show the 2D browser while in WebXR?
Quest Pro added the ability to bring up the browser while the user is in an immersive game. Would it make sense to allow this while in WebXR? What are the pitfalls? (ie should it show all tabs or only the active one)
The text was updated successfully, but these errors were encountered: