Skip to content
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

Cross origin content and input #21

Open
RafaelCintron opened this issue Mar 9, 2020 · 0 comments
Open

Cross origin content and input #21

RafaelCintron opened this issue Mar 9, 2020 · 0 comments

Comments

@RafaelCintron
Copy link

The spec has the following to say about cross origin content and input:

For a DOM overlay, XR input event data is treated as similar to mouse movement data. Poses remain available to the outer page if there is no cross-origin content, or if the cross-origin content is not receiving input, but are limited (blocked) when interacting with cross-origin content.

Does this mean the conforming UA must determine whether cross origin content is drawn anywhere inside of the DOM overlay element and, if so, stop returning all poses to the web developer? If so, that seems like a tough thing to determine for any random element. No?

In the context of VR DOM overlays, what does it mean for the cross-origin content to not receive input? Can the cross origin content only receive select-type input?

Can you please elaborate on the phase "but are limited (blocked) when interacting with cross-origin content"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant