Skip to content

Commit

Permalink
Address Domenic comments.
Browse files Browse the repository at this point in the history
  • Loading branch information
ArthurSonzogni committed Oct 19, 2020
1 parent 975e120 commit 7fe3708
Showing 1 changed file with 36 additions and 30 deletions.
66 changes: 36 additions & 30 deletions source
Expand Up @@ -80526,11 +80526,13 @@ interface <dfn>BarProp</dfn> {
<p class="note">Similarly, <code>Document</code>s in a <span>cross-origin isolated</span>
<span>agent cluster</span> are automatically origin-isolated. The `<code
data-x="http-origin-isolation">Origin-Isolation</code>` header might be useful as an additional
hint to implementations about resource allocation, since the
`<code>Cross-Origin-Opener-Policy</code>` and `<code>Cross-Origin-Embedder-Policy</code>` headers
used to achieve cross-origin isolation are more about ensuring that everything in the same address
space opts in to being there. But adding it would have no additional observable effects on author
code.</p>
hint to implementations about resource allocation, since the `<code
data-x="http-cross-origin-opener-policy">Cross-Origin-Opener-Policy</code>` and
`<code>Cross-Origin-Embedder-Policy</code>` headers used to achieve cross-origin isolation are
more about ensuring that everything in the same address space opts in to being there. But adding
it would have no additional observable effects on author code.</p>



<h3>Sandboxing</h3>

Expand Down Expand Up @@ -80891,19 +80893,18 @@ interface <dfn>BarProp</dfn> {
group">group</span>'s <span data-x="bcg cross-origin isolated">cross-origin isolated</span> to
true.</p>

<div class="note">
"<code data-x="coop-same-origin-plus-COEP">same-origin-plus-COEP</code>" cannot be directly
set via the `<code>Cross-Origin-Opener-Policy</code>` header, but results from a combination
of setting together:
<ul>
<li>`<code>Cross-Origin-Opener-Policy</code>:
<code data-x="coop-same-origin">same-origin</code>`
</li>
<li>`<code>Cross-Origin-Embedder-Policy</code>:
<code data-x="coep-require-corp">require-corp</code>`
</li>
</ul>
</div>
<p class="note">"<code data-x="coop-same-origin-plus-COEP">same-origin-plus-COEP</code>" cannot
be directly set via the
`<code data-x="http-cross-origin-opener-policy">Cross-Origin-Opener-Policy</code>` header,
but results from a combination of setting both
`<code data-x="">
<span data-x="http-cross-origin-opener-policy">Cross-Origin-Opener-Policy</span>:
<span data-x="coop-same-origin">same-origin</span>
</code>` and
`<code data-x="">
<span>Cross-Origin-Embedder-Policy</span>:
<span data-x="coep-require-corp">require-corp</span>
</code>` together.</p>
</dd>
</dl>

Expand All @@ -80925,10 +80926,12 @@ interface <dfn>BarProp</dfn> {
<li><p>Return false.</p></li>
</ol>

<h4>The `<code>Cross-Origin-Opener-Policy</code>` header</h4>
<h4>The `<code data-x="http-cross-origin-opener-policy">Cross-Origin-Opener-Policy</code>`
header</h4>

<p>A <code>Document</code>'s <span data-x="concept-document-coop">cross-origin opener
policy</span> is derived from the `<code>Cross-Origin-Opener-Policy</code>` HTTP response header.
policy</span> is derived from the `<code
data-x="http-cross-origin-opener-policy">Cross-Origin-Opener-Policy</code>` HTTP response header.
This header is a <span data-x="http-structured-header">structured header</span> whose value must
be a <span data-x="http-structured-header-token">token</span>. <ref spec=STRUCTURED-FIELDS></p>

Expand All @@ -80952,8 +80955,9 @@ interface <dfn>BarProp</dfn> {
"<code data-x="coop-unsafe-none">unsafe-none</code>".</p></li>

<li><p>Let <var>value</var> be the result of <span>getting a structured field value</span> given
`<code>Cross-Origin-Opener-Policy</code>` and "<code data-x="">item</code>" from
<var>response</var>'s <span data-x="concept-response-header-list">header list</span>.</p></li>
`<code data-x="http-cross-origin-opener-policy">Cross-Origin-Opener-Policy</code>` and "<code
data-x="">item</code>" from <var>response</var>'s <span
data-x="concept-response-header-list">header list</span>.</p></li>

<li><p>If <var>value</var> is null, then return "<code
data-x="coop-unsafe-none">unsafe-none</code>".</p></li>
Expand Down Expand Up @@ -81382,8 +81386,9 @@ interface <dfn>BarProp</dfn> {
href="https://github.com/whatwg/html/issues/4782">whatwg/html issue #4782</a> and <a
href="https://github.com/whatwg/html/issues/5350">whatwg/html issue #5350</a> for defining
<span>browsing session</span>. It is roughly analogous to a <span>top-level browsing
context</span> except that it cannot be replaced due to a
`<code>Cross-Origin-Opener-Policy</code>` header or navigation.</p>
context</span> except that it cannot be replaced due to a `<code
data-x="http-cross-origin-opener-policy">Cross-Origin-Opener-Policy</code>` header or
navigation.</p>

<p>A <span>top-level browsing context</span> has an associated <dfn export data-x="tlbc browsing
session" for="top-level browsing context">browsing session</dfn> which is a <span>browsing
Expand Down Expand Up @@ -93619,10 +93624,11 @@ interface mixin <dfn>WindowOrWorkerGlobalScope</dfn> {

<dt>self . <code subdfn data-x="dom-crossOriginIsolated">crossOriginIsolated</code></dt>
<dd><p>Returns whether scripts running in this global are allowed to use APIs that require
cross-origin isolation. This depends on the `<code>Cross-Origin-Opener-Policy</code>`
and `<code>Cross-Origin-Embedder-Policy</code>` HTTP response headers and the
"<code data-x="cross-origin-isolated-feature">cross-origin-isolated</code>"
feature.</p></dd>
cross-origin isolation. This depends on the
`<code data-x="http-cross-origin-opener-policy">Cross-Origin-Opener-Policy</code>` and
`<code>Cross-Origin-Embedder-Policy</code>` HTTP response headers and the
"<code data-x="cross-origin-isolated-feature">cross-origin-isolated </code>" feature.
</p></dd>
</dl>

<div class="example">
Expand Down Expand Up @@ -118270,7 +118276,8 @@ interface <dfn>External</dfn> {
</dl>


<h3>`<dfn http-header><code>Cross-Origin-Opener-Policy</code></dfn>`</h3>
<h3>`<dfn http-header><code data-x="http-cross-origin-opener-policy"> Cross-Origin-Opener-Policy
</code></dfn>`</h3>

<p>This section describes a header for registration in the Permanent Message Header Field
Registry. <ref spec=RFC3864></p>
Expand Down Expand Up @@ -123627,7 +123634,6 @@ INSERT INTERFACES HERE
Arne Thomassen,
Aron Spohr,
Arphen Lin,
Arthur Sonzogni, <!-- ArthurSonzogni on Github -->
Arthur Stolyar,
Arun Patole,
Aryeh Gregor,
Expand Down

0 comments on commit 7fe3708

Please sign in to comment.