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

Interoperability and compatibility - browser vendors & web developers support for DOM Overlay #16

Open
klausw opened this issue Feb 24, 2020 · 1 comment

Comments

@klausw
Copy link
Contributor

klausw commented Feb 24, 2020

I'm currently preparing to send out an Intent to Ship for WebXR DOM Overlays Module so I'd like to poll for other vendors' support for the module. @raviramachandra, @Manishearth, @thetuvix, @grorg, @kearwood and others - can you share your opinion please?

There's a currently an open issue (#15) about integration with Fullscreen API, I'm working on a PR to address this. (Unless I'm misunderstanding it, I think this is just a matter of clarifications and I'm not expecting API-level changes as a result of this.)

Web developers' opinion about this module is also welcome!

@dmarcos
Copy link

dmarcos commented Feb 24, 2020

This work is very welcome and the spec is a very nice starting point. Using the 2D DOM in immersive mode has been one of the most requested features by A-Frame devs. Easy ways to build HUDs, instructions, setting menus or Youtube embeds are in high demand and the DOM Overlay seems to happily cover those. Looking forward to integrating in A-Frame.

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

2 participants