Skip to content

Commit 590a022

Browse files
Make COOP+COEP do not imply crossOriginIsolated.
The [specification] currently requires [COOP] + [COEP] to give access to crossOriginIsolated capabilities like SharedArrayBuffer. Some platforms can't easily support multiple processes (like Android Webview). Therefore, they can't really support crossOriginIsolated. However the are no strong reasons for them not to enforce COEP (and maybe COOP) when their associated headers are present. It would be great enforcing COEP (and maybe COOP) on all platforms, desptie the lack of crossOriginIsolated capabilities. This patch makes the specification to allow (instead of requiring) platform to set the crossOriginIsolated flag when both COOP and COEP are used. Setting crossOriginIsolated becomes platform dependent. In exchange, we can enforce COEP (and COOP) in a non platform dependent way, without conflicting with the specification about crossOriginIsolated. [Bug]: #6060 [specification]: https://html.spec.whatwg.org/#cross-origin-opener-policies [COOP]: https://html.spec.whatwg.org/#cross-origin-opener-policy [COEP]: https://html.spec.whatwg.org/#coep
1 parent 895fd80 commit 590a022

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

source

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -80909,9 +80909,9 @@ interface <dfn>BarProp</dfn> {
8090980909
<dt>"<dfn><code data-x="coop-same-origin-plus-COEP">same-origin-plus-COEP</code></dfn>"</dt>
8091080910
<dd>
8091180911
<p>This behaves the same as "<code data-x="coop-same-origin">same-origin</code>", with the
80912-
addition that it sets the (new) <span>top-level browsing context</span>'s <span data-x="tlbc
80913-
group">group</span>'s <span data-x="bcg cross-origin isolated">cross-origin isolated</span> to
80914-
true.</p>
80912+
addition that, on platforms supporting it, it allows setting the (new) <span>top-level browsing
80913+
context</span>'s <span data-x="tlbc group">group</span>'s <span
80914+
data-x="bcg cross-origin isolated">cross-origin isolated</span> to true.</p>
8091580915

8091680916
<p class="note">"<code data-x="coop-same-origin-plus-COEP">same-origin-plus-COEP</code>" cannot
8091780917
be directly set via the `<code
@@ -80920,6 +80920,12 @@ interface <dfn>BarProp</dfn> {
8092080920
data-x="http-cross-origin-opener-policy">Cross-Origin-Opener-Policy</span>: <span
8092180921
data-x="coop-same-origin">same-origin</span></code>` and `<code
8092280922
data-x=""><span>Cross-Origin-Embedder-Policy</span>: require-corp</code>` together.</p>
80923+
80924+
<p class="note">"<code data-x="coop-same-origin-plus-COEP">same-origin-plus-COEP</code>" <b>
80925+
doesn't require</b> setting the <span>top-level browsing context</span>'s <span data-x="tlbc
80926+
group">group</span>'s <span data-x="bcg cross-origin isolated">cross-origin isolated</span> to
80927+
true. Whether this is sufficient or not is platform-specific. This is only a necessary
80928+
condition. It is not guaranteed to be sufficient.</p>
8092380929
</dd>
8092480930
</dl>
8092580931

0 commit comments

Comments
 (0)