-
Notifications
You must be signed in to change notification settings - Fork 74
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 title, url, and org of Permissions Policy (formerly Feature Policy) #348
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.
LGTM. Odd that the webappsec draft doesn't even mention "Feature Policy" as a string any more, e.g. in a "Changes" appendix summarizing changes since previous public draft. I may file an issue for them to do so unless there's a reason not to.
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.
Our remaining concerns are being addressed now (naming was one of them and this was our suggested solution), but maybe we should update that separately from this more editorial PR.
I might even go as far as suggesting this is important to us now as this cements the way we think about permissions and third-parties in general.
(I created a PR for Tantek's remark.)
I would support a change to "important" also. The URL of the spec remains the same, which is awkward. |
BTW, discussion about changing to |
Re: #348 (comment) Looking at this late -- the URL has changed (though the old one redirects) and is now canonically https://w3c.github.io/webappsec-permissions-policy/ |
Per #348 (comment) link directly to webappsec-permissions-policy
Per #348 (comment) link directly to webappsec-permissions-policy
(note that the sorting by title means the entry moves)