Rename Origin-Isolation to Origin-Agent-Cluster

Also renames the feature from "origin isolation" to "origin-keyed agent
clusters" and renames the getter from window.originIsolated to
window.originAgentCluster.

Closes #6192.

Author: domenic

source

@@ -77962,8 +77962,9 @@ console.assert(iframeWindow.frameElement === null);
   <p>A <span>browsing context group</span> has an associated <dfn>historical agent cluster key
   map</dfn>, which is a <span data-x="ordered map">map</span> of <span
   data-x="origin">origins</span> to <span data-x="agent cluster key">agent cluster keys</span>. This
-  map is used to ensure the consistency of the <a href="#origin-isolation">origin isolation</a>
-  feature by recording what agent cluster keys were previously used for a given origin.</p>
+  map is used to ensure the consistency of the <a href="#origin-keyed-agent-clusters">origin-keyed
+  agent clusters</a> feature by recording what agent cluster keys were previously used for a given
+  origin.</p>
 
   <p class="note">The <span>historical agent cluster key map</span> only ever gains entries over the
   lifetime of the browsing context group.</p>
@@ -78671,7 +78672,7 @@ interface <dfn interface>Window</dfn> : <span>EventTarget</span> {
 
   // the user agent
   readonly attribute <span>Navigator</span> <span data-x="dom-navigator">navigator</span>; <!-- IE also has window.clientInformation === window.navigator -->
-  readonly attribute boolean <span data-x="dom-originIsolated">originIsolated</span>;
+  readonly attribute boolean <span data-x="dom-originAgentCluster">originAgentCluster</span>;
 
   // user prompts
   undefined <span data-x="dom-alert">alert</span>();
@@ -80336,7 +80337,8 @@ interface <dfn>BarProp</dfn> {
     data-x="document-domain-feature">document-domain</code>" feature is disabled, the setter will
     throw a <span>"<code>SecurityError</code>"</span> exception. In cases where <code
     data-x="dom-crossOriginIsolated">crossOriginIsolated</code> or <code
-    data-x="dom-originIsolated">originIsolated</code> return true, the setter will do nothing.</p>
+    data-x="dom-originAgentCluster">originAgentCluster</code> return true, the setter will do
+    nothing.</p>
    </dd>
   </dl>
 
@@ -80397,8 +80399,8 @@ interface <dfn>BarProp</dfn> {
    <li><p>If the <span>surrounding agent</span>'s <span>agent cluster</span>'s <span>cross-origin
    isolated</span> is true, then return.</p></li>
 
-   <li><p>If the <span>surrounding agent</span>'s <span>agent cluster</span>'s
-   <span>origin-isolated</span> is true, then return.</p></li>
+   <li><p>If the <span>surrounding agent</span>'s <span>agent cluster</span>'s <span>is
+   origin-keyed</span> is true, then return.</p></li>
 
    <li><p>Set <var>this</var>'s <span>origin</span>'s <span
    data-x="concept-origin-domain">domain</span> to the result of <span data-x="host
@@ -80448,22 +80450,24 @@ interface <dfn>BarProp</dfn> {
 
 
 
-  <h4>Origin isolation</h4>
+  <h4><span id="origin-isolation"></span>Origin-keyed agent clusters</h4>
 
   <dl class="domintro">
-   <dt>window . <code subdfn data-x="dom-originIsolated">originIsolated</code></dt>
+   <dt>window . <code subdfn data-x="dom-originAgentCluster">originAgentCluster</code></dt>
 
    <dd>
-    <p>Returns true if this <code>Window</code> is origin-isolated in the manner described in this
-    section.</p>
+    <p>Returns true if this <code>Window</code> belongs to an <span>agent cluster</span> which is
+    <span>origin</span>-<span data-x="agent cluster key">keyed</span>, in the manner described in
+    this section.</p>
    </dd>
   </dl>
 
-  <p>A <code>Document</code> delivered over a <span>secure context</span> can opt in to origin
-  isolation, by using the `<code data-x="http-origin-isolation">Origin-Isolation</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-boolean">boolean</span>. <ref
-  spec=STRUCTURED-FIELDS></p>
+  <p>A <code>Document</code> delivered over a <span>secure context</span> can request that it be
+  placed in an <span>origin</span>-<span data-x="agent cluster key">keyed</span> <span>agent
+  cluster</span>, by using the `<code
+  data-x="http-origin-agent-cluster">Origin-Agent-Cluster</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-boolean">boolean</span>. <ref spec=STRUCTURED-FIELDS></p>
 
   <p><span w-nodev>Per the processing model in the <span data-x="create-the-document-object">create
   and initialize a new <code>Document</code> object</span>, values</span><span
@@ -80482,28 +80486,30 @@ interface <dfn>BarProp</dfn> {
   efficiently.</p>
 
   <p>Note that within a <span>browsing context group</span>, the `<code
-  data-x="http-origin-isolation">Origin-Isolation</code>` header can never cause same-origin
+  data-x="http-origin-agent-cluster">Origin-Agent-Cluster</code>` header can never cause same-origin
   <code>Document</code> objects to end up in different <span data-x="agent cluster">agent
   clusters</span>, even if one sends the header and the other doesn't.<span w-nodev> This is
   prevented by means of the <span>historical agent cluster key map</span>.</span></p>
 
-  <p class="note">This means that the <code data-x="dom-originIsolated">originIsolated</code> getter
-  can return false, even if the header is set, if the header was omitted on a previously-loaded
-  same-origin page in the same <span>browsing context group</span>. Similarly, it can return true
-  even when the header is not set.</p>
+  <p class="note">This means that the <code
+  data-x="dom-originAgentCluster">originAgentCluster</code> getter can return false, even if the
+  header is set, if the header was omitted on a previously-loaded same-origin page in the same
+  <span>browsing context group</span>. Similarly, it can return true even when the header is not
+  set.</p>
 
-  <p w-nodev>The <dfn><code data-x="dom-originIsolated">originIsolated</code></dfn> getter steps are
-  to return the <span>surrounding agent</span>'s <span>agent cluster</span>'s
-  <span>origin-isolated</span>.</p>
+  <p w-nodev>The <dfn><code data-x="dom-originAgentCluster">originAgentCluster</code></dfn> getter
+  steps are to return the <span>surrounding agent</span>'s <span>agent cluster</span>'s <span>is
+  origin-keyed</span>.</p>
 
   <p class="note"><code>Document</code>s with an <span data-x="concept-origin-opaque">opaque
-  origin</span> can be considered unconditionally origin-isolated; for them the header has no
-  effect.</p>
+  origin</span> can be considered unconditionally origin-keyed; for them the header has no effect,
+  and the <code data-x="dom-originAgentCluster">originAgentCluster</code> getter will always return
+  true.</p>
 
   <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
+  <span>agent cluster</span> are automatically origin-keyed. The `<code
+  data-x="http-origin-agent-cluster">Origin-Agent-Cluster</code>` header might be useful as an
+  additional 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
@@ -84957,23 +84963,23 @@ interface <dfn>Location</dfn> { // but see also <a href="#the-location-interface
     <p>Otherwise:</p>
 
     <ol>
-     <li><p>Let <var>oiHeader</var> be the result of <span>getting a structured field value</span>
-     given `<code data-x="http-origin-isolation">Origin-Isolation</code>` and "<code
+     <li><p>Let <var>oacHeader</var> be the result of <span>getting a structured field value</span>
+     given `<code data-x="http-origin-agent-cluster">Origin-Agent-Cluster</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>Let <var>requestsOI</var> be true if <var>oiHeader</var> is not
-     null and <var>oiHeader</var>[0] is the <span
+     <li><p>Let <var>requestsOAC</var> be true if <var>oacHeader</var> is not
+     null and <var>oacHeader</var>[0] is the <span
      data-x="http-structured-header-boolean">boolean</span> true; otherwise false.</p></li>
 
      <li><p>If <var>reservedEnvironment</var> is a <span>non-secure context</span>, then set
-     <var>requestsOI</var> to false.</p></li>
+     <var>requestsOAC</var> to false.</p></li>
 
      <li><p>Let <var>agent</var> be the result of <span
      data-x="obtain-similar-origin-window-agent">obtaining a similar-origin window agent</span>
      given <var>navigationParams</var>'s <span data-x="navigation-params-origin">origin</span>,
      <var>browsingContext</var>'s <span data-x="tlbc group">group</span>, and
-     <var>requestsOI</var>.</p></li>
+     <var>requestsOAC</var>.</p></li>
 
      <li>
       <p>Let <var>realm execution context</var> be the result of <span>creating a new JavaScript
@@ -86795,7 +86801,7 @@ interface <dfn>BeforeUnloadEvent</dfn> : <span>Event</span> {
   <p>An <span>agent cluster</span> has an associated <dfn>cross-origin isolated</dfn> (a boolean),
   which is initially false.</p>
 
-  <p>An <span>agent cluster</span> has an associated <dfn>origin-isolated</dfn> (a boolean), which
+  <p>An <span>agent cluster</span> has an associated <dfn>is origin-keyed</dfn> (a boolean), which
   is initially false.</p>
 
   <hr>
@@ -86805,14 +86811,15 @@ interface <dfn>BeforeUnloadEvent</dfn> : <span>Event</span> {
 
   <p>An <dfn>agent cluster key</dfn> is a <span>site</span> or <span
   data-x="concept-origin-tuple">tuple origin</span>. Without web developer action to achieve <a
-  href="#origin-isolation">origin isolation</a>, it will be a <span>site</span>.</p>
+  href="#origin-keyed-agent-clusters">origin-keyed agent clusters</a>, it will be a
+  <span>site</span>.</p>
 
   <p class="note">An equivalent formulation is that an <span>agent cluster key</span> can be a
   <span>scheme-and-host</span> or an <span>origin</span>.</p>
 
   <p>To <dfn data-x="obtain-similar-origin-window-agent">obtain a similar-origin window agent</dfn>,
   given an <span>origin</span> <var>origin</var>, a <span>browsing context group</span>
-  <var>group</var>, and a boolean <var>requestsOI</var>, run these steps:</p>
+  <var>group</var>, and a boolean <var>requestsOAC</var>, run these steps:</p>
 
   <ol>
    <li><p>Let <var>site</var> be the result of <span data-x="obtain a site">obtaining a site</span>
@@ -86831,7 +86838,8 @@ interface <dfn>BeforeUnloadEvent</dfn> : <span>Event</span> {
     <p>Otherwise:</p>
 
     <ol>
-     <li><p>If <var>requestsOI</var> is true, then set <var>key</var> to <var>origin</var>.</p></li>
+     <li><p>If <var>requestsOAC</var> is true, then set <var>key</var> to
+     <var>origin</var>.</p></li>
 
      <li><p>Set <var>group</var>'s <span>historical agent cluster key map</span>[<var>origin</var>]
      to <var>key</var>.</p></li>
@@ -86848,7 +86856,7 @@ interface <dfn>BeforeUnloadEvent</dfn> : <span>Event</span> {
      <li><p>Set <var>agentCluster</var>'s <span>cross-origin isolated</span> to <var>group</var>'s
      <span data-x="bcg cross-origin isolated">cross-origin isolated</span>.</p></li>
 
-     <li><p>Set <var>agentCluster</var>'s <span>origin-isolated</span> to true if <var>key</var>
+     <li><p>Set <var>agentCluster</var>'s <span>is origin-keyed</span> to true if <var>key</var>
      equals <var>origin</var>; otherwise false.</p></li>
 
      <li><p>Add the result of <span data-x="create an agent">creating an agent</span>, given false,
@@ -86887,11 +86895,11 @@ interface <dfn>BeforeUnloadEvent</dfn> : <span>Event</span> {
      <li><p>Set <var>agentCluster</var> to a new <span>agent cluster</span>.</p></li>
 
      <li>
-      <p>Set <var>agentCluster</var>'s <span>origin-isolated</span> to true.</p>
+      <p>Set <var>agentCluster</var>'s <span>is origin-keyed</span> to true.</p>
 
-      <p class="note">These workers can be considered to be origin-isolated. However, this is not
+      <p class="note">These workers can be considered to be origin-keyed. However, this is not
       exposed through any APIs (in the way that <code
-      data-x="dom-originIsolated">originIsolated</code> exposes the origin-isolation state for
+      data-x="dom-originAgentCluster">originAgentCluster</code> exposes the origin-keyedness for
       windows).</p>
      </li>
     </ol>
@@ -117653,14 +117661,14 @@ interface <dfn>External</dfn> {
   </dl>
 
 
-  <h3>`<dfn><code data-x="http-origin-isolation">Origin-Isolation</code></dfn>`</h3>
+  <h3>`<dfn><code data-x="http-origin-agent-cluster">Origin-Agent-Cluster</code></dfn>`</h3>
 
   <p>This section describes a header for registration in the Permanent Message Header Field
   Registry. <ref spec=RFC3864></p>
 
   <dl>
    <dt>Header field name:</dt>
-   <dd>Origin-Isolation</dd>
+   <dd>Origin-Agent-Cluster</dd>
    <dt>Applicable protocol:</dt>
    <dd>http</dd>
    <dt>Status:</dt>