8000 Define how feature requirements are satisfied by toji · Pull Request #839 · immersive-web/webxr · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
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

Define how feature requirements are satisfied #839

Merged
merged 1 commit into from
Sep 12, 2019
Merged

Conversation

toji
Copy link
Member
@toji toji commented Sep 12, 2019

Fixes #790. Defines more precisely what level of confidence a UA must
have that a feature can be supported by a given XR device before
creating a session that requires said feature.

Fixes #790. Defines more precisely what level of confidence a UA must
have that a feature can be supported by a given XR device before
creating a session that requires said feature.
@toji toji requested a review from NellWaliczek September 12, 2019 00:15
@toji toji merged commit 79c80e8 into master Sep 12, 2019
@toji toji deleted the required-requirements branch September 12, 2019 18:36
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

Successfully merging this pull request may close these issues.

Clarify when a requiredFeature is allowed to pass
2 participants
0