Skip to content

Block mid-session consent requests #767

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

Merged
merged 2 commits into from
Jul 19, 2019
Merged

Block mid-session consent requests #767

merged 2 commits into from
Jul 19, 2019

Conversation

toji
Copy link
Member

@toji toji commented Jul 17, 2019

/fixes #751

Details that consent dialogs may not be displayed while an immersive
session is active, and explains that this is a short-term restriction.

I chose to go with terminating the session in this case rather than
suppressing the consent dialog altogether, since it provides very clear
feedback about the error case and doesn't require us to make up new
behavior for the permissions in question.

/fixes #751

Details that consent dialogs may not be displayed while an immersive
session is active, and explains that this is a short-term restriction.

I chose to go with terminating the session in this case rather than
suppressing the consent dialog altogether, since it provides very clear
feedback about the error case and doesn't require us to make up new
behavior for the permissions in question.
@toji toji added this to the June 2019 milestone Jul 17, 2019
@toji
Copy link
Member Author

toji commented Jul 17, 2019

Also pinging @blairmacintyre, though I couldn't add you as a reviewer since you haven't been explicitly added as a collaborator for this repo. (We can change that if you'd like!)

index.bs Outdated

There are multiple non-XR APIs which cause user agents to request [=explicit consent=] to use a feature. If the user agent will request the user's consent while there is an [=active immersive session=], the user agent MUST [=shut down the session=] prior to displaying the consent request to the user. If the user's consent for the feature had been granted prior to the [=active immersive session=] being created the session does not need to be terminated.

Note: This limitation is to ensure that there is behavioral parity between all user agents until consensus is reached about how to securely display these types of prompts. It is not expected to be a long term requirement.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I particularly appreciate that the motivation is spelled out. Thank you!

@blairmacintyre
Copy link
Contributor

Looks good. (And I'm happy to be a collaborator)

Co-Authored-By: johnpallett <johnpallett@google.com>
Copy link
Member

@NellWaliczek NellWaliczek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Glad we were able to reach consensus on this temporary measure!

@toji toji merged commit 8eaae9e into master Jul 19, 2019
@toji toji deleted the mid-session-consent branch July 19, 2019 16:23
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.

For now, block mid-session consent requests for non-xr features
4 participants