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.

Sign up for GitHub

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

Jump to bottom

Discussion needed: Which buttons should be reserved for browser functionality for input profiles? #159

Open
fordacious opened this issue Jan 28, 2020 · 0 comments
Open

Discussion needed: Which buttons should be reserved for browser functionality for input profiles? #159

fordacious opened this issue Jan 28, 2020 · 0 comments
Labels
registry Registry package
Milestone
Next Release

Comments

@fordacious
Copy link
Contributor

The OpenXR implementation of WebXR in Chromium 81 currently reserves a menu button for each interaction profile. The buttons were chosen based on available menu buttons and the B-button for the index controller (on advice from Valve). Are these the correct buttons to canonize and reserve for browser functionality?

The PR for this change is #158
@fordacious fordacious added the registry Registry package label Jan 28, 2020
@toji toji added this to the Next Release milestone Feb 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
registry Registry package
Projects
None yet
Milestone
Next Release
Development

No branches or pull requests
2 participants
@fordacious @toji