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

Querying user consent status #722

Closed
NellWaliczek opened this issue Jun 19, 2019 · 4 comments · Fixed by #900
Closed

Querying user consent status #722

NellWaliczek opened this issue Jun 19, 2019 · 4 comments · Fixed by #900
Assignees
Labels
consent tracking All things related to acquiring and communicating user consent fixed by pending PR A PR that is in review will resolve this issue. privacy-and-security Issues related to privacy and security
Milestone

Comments

@NellWaliczek
Copy link
Member

[Disclaimer: This issue is one of several being filed to capture discussions that began either on #638, on #689, or at the most recent F2F]

This issue is dependent on the outcome of #720. If it is possible to request user consent in the middle of an immersive session, developers will likely need a way to determine if an API call will trigger a consent prompt so that they can explain to the end user that this will happen. For non-XR features, the Permissions API services this need via the query() API.

This issue tracks the need to determine if WebXR should allow for the ability to check if a prompt will be shown. It also track the discussion about what (if any) relationship WebXR should have with the existing Permissions API.

(Note, this issue will probably be one of the later ones that gets solved out of this batch as it is dependent on a number of others landing first)

@ddorwin
Copy link
Contributor

ddorwin commented Jun 20, 2019

The answer likely depends on the answer to #725.

@cwilso cwilso modified the milestones: July 2019, August 2019 Jul 8, 2019
@NellWaliczek NellWaliczek self-assigned this Jul 31, 2019
@NellWaliczek NellWaliczek added the consent tracking All things related to acquiring and communicating user consent label Sep 5, 2019
@Manishearth
Copy link
Contributor

/agenda to be discussed alongside #725

@probot-label probot-label bot added the agenda Request discussion in the next telecon/FTF label Sep 30, 2019
@AdaRoseCannon AdaRoseCannon removed the agenda Request discussion in the next telecon/FTF label Oct 8, 2019
@Manishearth
Copy link
Contributor

We seem to be leaning towards the direction of relying on the existing permissions API to some extent at least, so there's a good chance this issue will be unnecessary, based on what we settle on.

@probot-label probot-label bot added the fixed by pending PR A PR that is in review will resolve this issue. label Nov 6, 2019
@probot-label
Copy link

probot-label bot commented Nov 6, 2019

This issue is fixed by PR #900

@toji toji modified the milestones: October 2019, November 2019 Nov 18, 2019
@toji toji modified the milestones: December 2019, Pre-CR Feb 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
consent tracking All things related to acquiring and communicating user consent fixed by pending PR A PR that is in review will resolve this issue. privacy-and-security Issues related to privacy and security
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants