Require all owning documents to have permission policy enabled - #239
Conversation
|
Failure is due to respec.org being down! |
rakuco
left a comment
There was a problem hiding this comment.
The idea sounds good, I wonder if this spec is the first to implement this kind of check.
Can you mention this novel approach in the "Policy control" section? Maybe it's worth discussing it in "Mitigation strategies" too.
| </ol> | ||
| </li> | ||
| <aside class="issue"> | ||
| <a href="https://github.com/wicg/compute-pressure/issues/110"> |
There was a problem hiding this comment.
| <a href="https://github.com/wicg/compute-pressure/issues/110"> | |
| <a href="https://github.com/w3c/compute-pressure/issues/110"> |
| <a href="https://github.com/wicg/compute-pressure/issues/110"> | ||
| Permission policy doesn't support workers yet #110 | ||
| </a> | ||
| Permission policy doesn't support workers directly yet #110</a>, so they cannot be set per |
There was a problem hiding this comment.
| Permission policy doesn't support workers directly yet #110</a>, so they cannot be set per | |
| Permission policy does not support workers directly yet (#110)</a>, so they cannot be set per |
| Shared workers often have multiple owning documents as they can be obtained | ||
| by other documents with the [=same origin=]. | ||
|
|
||
| In this case, all owning documents have to have the permission policy allowed |
There was a problem hiding this comment.
Is "have the permission policy allowed" a common way of phrasing this? It sounds a bit confusing.
There was a problem hiding this comment.
Yeah, I tried changing it a few times, but didn't find a good wording :-) Maybe @anssiko has some good suggestions
There was a problem hiding this comment.
How about just using allowed to use like in observe()?
"[...] all owning documents must be allowed to use the policy-controlled feature defined by this specification", for example.
Co-authored-by: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
@rakuco
Preview | Diff