Give the UA permission to return anything it wants from query(). #97
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The main constraint is that the result can only change when the UA gets new information about the user's intent.
…permission state".
| more detailed structure that requires more information to describe it. In | ||
| that case, they should define a customized <a>permission descriptor | ||
| type</a> dictionary that inherits from {{PermissionDescriptor}}. | ||
| Each powerful feature has one or more aspects that websites may request |
There was a problem hiding this comment.
nit: link to "powerful features" dfn?
There was a problem hiding this comment.
nit: please avoid using "may" without a conforming product. Maybe we can just say "websites can request"?
There was a problem hiding this comment.
I don't think there is a definition of "powerful features". It used to be in Secure Contexts, but it got taken out. I was going back and forth on adding a "Definitions" section in this patch, but I guess I'll do it for this one.
And I've switched to "can".
|
Few comments, nits, etc. Thanks for putting this PR together @jyasskin! |
|
Yes, this is good. You should merge this and we can iterate on the outcome. |
This was referenced Jun 8, 2016
jyasskin
added a commit
to jyasskin/web-bluetooth-1
that referenced
this pull request
Jul 15, 2016
Lots of terminology changed in w3c/permissions#97.
jyasskin
added a commit
to jyasskin/web-bluetooth-1
that referenced
this pull request
Jul 15, 2016
Lots of terminology changed in w3c/permissions#97.
jyasskin
added a commit
to jyasskin/web-bluetooth-1
that referenced
this pull request
Jul 15, 2016
Lots of terminology changed in w3c/permissions#97.
jyasskin
added a commit
to jyasskin/web-bluetooth-1
that referenced
this pull request
Jul 18, 2016
Lots of terminology changed in w3c/permissions#97.
jyasskin
added a commit
to jyasskin/web-bluetooth-1
that referenced
this pull request
Jul 18, 2016
Lots of terminology changed in w3c/permissions#97.
jyasskin
added a commit
to jyasskin/web-bluetooth-1
that referenced
this pull request
Jul 18, 2016
Lots of terminology changed in w3c/permissions#97.
This was referenced Jul 19, 2016
jyasskin
added a commit
to jyasskin/web-bluetooth-1
that referenced
this pull request
Jul 20, 2016
Lots of terminology changed in w3c/permissions#97.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This option is the most straightforward about giving the UA nearly complete flexibility. The main constraint is that the result should only change when the UA gets new information about the user's intent, but we don't say what constitutes new information. This version also gives some examples (media and durable storage) of constraining permission behavior further on a per-API basis.
Preview at https://api.csswg.org/bikeshed/?url=https://raw.githubusercontent.com/jyasskin/permissions/ua-can-return-anything/index.bs