Cleanup priv-sec wording + recommend an indicator #323
Conversation
index.html
Outdated
| </h2> | ||
| <p> | ||
| The `"screen-wake-lock"` <a>powerful feature</a> defines a | ||
| <a>permission revocation algorithm</a>. To invoke the <dfn>Screen |
There was a problem hiding this comment.
I started referencing the "permission revocation algorithm" in #297 to make sure this was properly integrated with the Permissions API spec. The new "revoke the screen-wake-lock permission" definition above is not referenced anywhere and it's not clear how it would integrate with the Permissions API.
There was a problem hiding this comment.
The Permissions API provides a permission revocation algorithm hook for specifications to take action when a permission is revoked. The definition above should be declared as the permission revocation algorithm for the "screen-wake-lock" permission.
index.html
Outdated
| </h2> | ||
| <p> | ||
| The `"screen-wake-lock"` <a>powerful feature</a> defines a | ||
| <a>permission revocation algorithm</a>. To invoke the <dfn>Screen |
There was a problem hiding this comment.
The Permissions API provides a permission revocation algorithm hook for specifications to take action when a permission is revoked. The definition above should be declared as the permission revocation algorithm for the "screen-wake-lock" permission.
Co-authored-by: Reilly Grant <reillyeon@users.noreply.github.com>
marcoscaceres
force-pushed
the
sec_wording
branch
from
e7d65c4
to
c4c634e
Compare
marcoscaceres
changed the title
marcoscaceres
changed the title
marcoscaceres
requested review from
rakuco and
reillyeon
and removed request for
kenchris
|
sorry for my screwup on this PR! Now only deals with #282. |
There was a problem hiding this comment.
lgtm. It'd be good for either @David-Chadwick or @reillyeon to take another look as well.
I think that's fine. I'm sure if it becomes an issue, users will get notified one way or another. |
…level. Follow-up to commit 0080849 ('Cleanup priv-sec wording + recommend an indicator (w3c#323)'). @David-Chadwick suggested adding this part of the original text back because it is still relevant (see w3c#323).
…level. (#328) Follow-up to commit 0080849 ('Cleanup priv-sec wording + recommend an indicator (#323)'). @David-Chadwick suggested adding this part of the original text back because it is still relevant (see #323).
Closes #282
Preview | Diff