-
Notifications
You must be signed in to change notification settings - Fork 72
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
Update Permissions Policy position per recent developments #450
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems good but I don't think I can merge PRs in this repo :)
activities.json
Outdated
@@ -799,7 +799,7 @@ | |||
"id": "feature-policy", | |||
"mozBugUrl": "https://bugzilla.mozilla.org/show_bug.cgi?id=1390801", | |||
"mozPosition": "worth prototyping", | |||
"mozPositionDetail": "Mozilla's primary interest in this specification is in the delegation of permissions to third-party contexts, and in particular permissions that might require the user to make a choice. To that end we are willing to prototype and ship the allow attribute, but given this reduction in scope the remaining functionality needs to be reevaluated in terms of naming and applicability.", | |||
"mozPositionDetail": "Mozilla's primary interest in this specification is in the delegation of permissions to third-party contexts that are not granted there by default. To that end we have shipped the allow attribute. The recently revised Permissions-Policy header seems worth prototyping and would allow for sites to impose restrictions on themselves. We hope that the API can be folded into the Permissions API and have not evaluated the reporting functionality as of yet.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe
We hope that the JavaScript API can be folded into the Permissions API
or DOM API or something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you add that before both occurrences of API? I guess I could do that, but I'm not sure if we consistently do that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I would think that it's clear from context after the first use.
If we consistently associate "API" with DOM/JS API on the page then that's fine. It just took me a little more time to parse the meaning of that sentence because I associated "the API" to be synonymous with "Permissions Policy as a whole", but it's really not that important :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed with clarifying "the API" to disambiguate. That's worth capturing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is sufficient detail. For any more detail folks can view #24. Thanks
Closes #24.
cc @johannhof