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

Allow features to be marked as deferrable #740

Closed
NellWaliczek opened this issue Jun 26, 2019 · 5 comments
Closed

Allow features to be marked as deferrable #740

NellWaliczek opened this issue Jun 26, 2019 · 5 comments
Assignees
Labels
consent tracking All things related to acquiring and communicating user consent privacy-and-security Issues related to privacy and security

Comments

@NellWaliczek
Copy link
Member

In the discussion on #720 (comment), we came to the conclusion that consensus had been established on Optional and Required features as described in #723, but not on the requirements for Deferrable features. This issue is intended tracks adding Deferrable features to the spec when the outstanding questions have been addressed. Based on my understanding, those questions are:

Any other considerations I'm missing?

@NellWaliczek NellWaliczek added this to the July 2019 milestone Jun 26, 2019
@NellWaliczek NellWaliczek added the privacy-and-security Issues related to privacy and security label Jun 26, 2019
@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
@avadacatavra
Copy link

avadacatavra commented Sep 17, 2019

It seems like if we decide to do this, then deferrable features aren't necessary

A UA would have three options for a mid-session prompt:

  1. Ignore it and continue with the session as instantiated (probably not a great path since it would encourage devs to frontload consent requests)
  2. Use a trusted immersive UI to handle the prompt
  3. Pause immersive mode, handle the prompt, then reenter immersive mode

@kearwood
Copy link
Contributor

Mozilla intends to implement permissions prompts that can appear at any time (including during active XR sessions). For FxR, this means that deferred sessions will not be required. There may be a short period where mid-session prompts may be ignored, prior to such an implementation which will be added ASAP.

@kearwood
Copy link
Contributor

The initial FxR implementation will be taking the #3 option (Pause immersive mode, handle the prompt, then reenter immersive mode). Later updates to FxR may implement #2 also.

@avadacatavra
Copy link

Ok, so let's ask for consensus on this.

It sounds like most UAs don't feel that they need deferred features, because they will take one of two paths:

  1. Use a trusted immersive UI to handle the prompt
  2. Use a trusted non-immersive UI, pausing the immersive session, to handle the prompt

If the UAs can comment here on whether they need deferred features, that would be great

@Manishearth
Copy link
Contributor

No UAs seem to have spoken up about a need for this, and we see a clear path for adding this backwards compatibly in the future if a UA does need it. Closing for now.

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 privacy-and-security Issues related to privacy and security
Projects
None yet
Development

No branches or pull requests

5 participants