-
Notifications
You must be signed in to change notification settings - Fork 386
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
Comments
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:
|
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. |
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:
If the UAs can comment here on whether they need deferred features, that would be great |
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. |
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?
The text was updated successfully, but these errors were encountered: