Editorial: use realms around 'incumbent'

source

@@ -106766,23 +106766,23 @@ new PaymentRequest(…); // Allowed to use
   callback">cleaning up after running a callback</span>, this value will be incremented and
   decremented.</p>
 
-  <p>Every <span>event loop</span> has an associated <dfn>backup incumbent settings object
-  stack</dfn>, initially empty. Roughly speaking, it is used to determine the <span>incumbent
-  settings object</span> when no author code is on the stack, but author code is responsible for the
-  current algorithm having been run in some way. The process of <span data-x="prepare to run a
-  callback">preparing to run a callback</span> and <span data-x="clean up after running a
-  callback">cleaning up after running a callback</span> manipulate this stack. <ref>WEBIDL</ref></p>
+  <p>Every <span>event loop</span> has an associated <dfn>backup incumbent realm stack</dfn>,
+  initially empty. Roughly speaking, it is used to determine the <span
+  data-x="concept-incumbent-realm">incumbent realm</span> when no author code is on the stack, but
+  author code is responsible for the current algorithm having been run in some way.
+  The process of <span data-x="prepare to run a callback">preparing to run a callback</span> and
+  <span data-x="clean up after running a callback">cleaning up after running a callback</span>
+  manipulate this stack. <ref>WEBIDL</ref></p>
 
   <p>When Web IDL is used to <span data-x="es-invoking-callback-functions">invoke</span> author
   code, or when <span>HostEnqueuePromiseJob</span> invokes a promise job, they use the following
-  algorithms to track relevant data for determining the <span>incumbent settings object</span>:</p>
+  algorithms to track relevant data for determining the <span
+  data-x="concept-incumbent-realm">incumbent realm</span>:</p>
 
-  <p>To <dfn export>prepare to run a callback</dfn> with an <span>environment settings object</span>
-  <var>settings</var>:</p>
+  <p>To <dfn export>prepare to run a callback</dfn> with a <span>realm</span> <var>realm</var>:</p>
 
   <ol>
-   <li><p>Push <var>settings</var> onto the <span>backup incumbent settings object
-   stack</span>.</p></li>
+   <li><p>Push <var>realm</var> onto the <span>backup incumbent realm stack</span>.</p></li>
 
    <li><p>Let <var>context</var> be the <span>topmost script-having execution
    context</span>.</p></li>
@@ -106791,8 +106791,8 @@ new PaymentRequest(&hellip;); // Allowed to use
    <span>skip-when-determining-incumbent counter</span>.</p></li>
   </ol>
 
-  <p>To <dfn export>clean up after running a callback</dfn> with an <span>environment settings
-  object</span> <var>settings</var>:</p>
+  <p>To <dfn export>clean up after running a callback</dfn> with a <span>realm</span>
+  <var>realm</var>:</p>
 
   <ol>
    <li>
@@ -106806,19 +106806,18 @@ new PaymentRequest(&hellip;); // Allowed to use
    <li><p>If <var>context</var> is not null, decrement <var>context</var>'s
    <span>skip-when-determining-incumbent counter</span>.</p></li>
 
-   <li><p><span>Assert</span>: the topmost entry of the <span>backup incumbent settings object
-   stack</span> is <var>settings</var>.</p></li>
+   <li><p><span>Assert</span>: the topmost entry of the <span>backup incumbent realm stack</span> is
+   <var>realm</var>.</p></li>
 
-   <li><p>Remove <var>settings</var> from the <span>backup incumbent settings object
-   stack</span>.</p></li>
+   <li><p>Remove <var>realm</var> from the <span>backup incumbent realm stack</span>.</p></li>
   </ol>
 
   <p>Here, the <dfn>topmost script-having execution context</dfn> is the topmost entry of the
   <span>JavaScript execution context stack</span> that has a non-null ScriptOrModule component, or
   null if there is no such entry in the <span>JavaScript execution context stack</span>.</p>
 
-  <p>With all this in place, the <dfn export>incumbent settings object</dfn> is determined as
-  follows:</p>
+  <p>With all this in place, the <dfn export data-x="concept-incumbent-realm">incumbent realm</dfn>
+  is determined as follows:</p>
 
   <ol>
    <li><p>Let <var>context</var> be the <span>topmost script-having execution
@@ -106830,31 +106829,29 @@ new PaymentRequest(&hellip;); // Allowed to use
 
     <ol>
      <li>
-      <p><span>Assert</span>: the <span>backup incumbent settings object stack</span> is not
-      empty.</p>
-
-      <p class="note">This assert would fail if you try to obtain the <span>incumbent settings
-      object</span> from inside an algorithm that was triggered neither by <a
-      href="#calling-scripts">calling scripts</a> nor by Web IDL <span
-      data-x="es-invoking-callback-functions">invoking</span> a callback. For example, it would
-      trigger if you tried to obtain the <span>incumbent settings object</span> inside an algorithm
-      that ran periodically as part of the <span>event loop</span>, with no involvement of author
-      code. In such cases the <span data-x="concept-incumbent-everything">incumbent</span> concept
-      cannot be used.</p>
+      <p><span>Assert</span>: the <span>backup incumbent realm stack</span> is not empty.</p>
+
+      <p class="note">This assert would fail if you try to obtain the <span
+      data-x="concept-incumbent-realm">incumbent realm</span> from inside an algorithm that was
+      triggered neither by <a href="#calling-scripts">calling scripts</a> nor by Web IDL <span
+      data-x="es-invoking-callback-functions">invoking</span> a callback.
+      For example, it would trigger if you tried to obtain the <span
+      data-x="concept-incumbent-realm">incumbent realm</span> inside an algorithm that ran
+      periodically as part of the <span>event loop</span>, with no involvement of author code.
+      In such cases the <span data-x="concept-incumbent-everything">incumbent</span> concept cannot
+      be used.</p>
      </li>
 
-     <li><p>Return the topmost entry of the <span>backup incumbent settings object
-     stack</span>.</p></li>
+     <li><p>Return the topmost entry of the <span>backup incumbent realm stack</span>.</p></li>
     </ol>
    </li>
 
-   <li><p>Return <var>context</var>'s Realm component's <span
-   data-x="concept-realm-settings-object">settings object</span>.</p></li>
+   <li><p>Return <var>context</var>'s Realm component.</p></li>
   </ol>
 
-  <p>Then, the <dfn export data-x="concept-incumbent-realm">incumbent realm</dfn> is the <span
-  data-x="environment settings object's realm">realm</span> of the <span>incumbent settings
-  object</span>.</p>
+  <p>Then, the <dfn export>incumbent settings object</dfn> is the
+  <span data-x="concept-incumbent-realm">incumbent realm</span>'s
+  <span data-x="concept-realm-settings-object">settings object</span>.</p>
 
   <p>Similarly, the <dfn export data-x="concept-incumbent-global">incumbent global object</dfn> is
   the <span data-x="concept-settings-object-global">global object</span> of the <span>incumbent
@@ -106874,10 +106871,10 @@ new PaymentRequest(&hellip;); // Allowed to use
   frames[0].postMessage("some data", "*");
 &lt;/script></code></pre>
 
-   <p>There are two interesting <span data-x="environment settings object">environment settings
-   objects</span> here: that of <code data-x="">window</code>, and that of <code
-   data-x="">frames[0]</code>. Our concern is: what is the <span>incumbent settings object</span> at
-   the time that the algorithm for <code data-x="dom-window-postMessage">postMessage()</code>
+   <p>There are two interesting <span data-x="realm">realms</span> here: that of
+   <code data-x="">window</code>, and that of <code data-x="">frames[0]</code>.
+   Our concern is: what is the <span data-x="concept-incumbent-realm">incumbent realm</span> at the
+   time that the algorithm for <code data-x="dom-window-postMessage">postMessage()</code>
    executes?</p>
 
    <p>It should be that of <code data-x="">window</code>, to capture the intuitive notion that the
@@ -106927,15 +106924,15 @@ new PaymentRequest(&hellip;); // Allowed to use
    <p>This time, the result involves more complicated mechanisms:</p>
 
    <p>When <code data-x="">bound</code> is <span data-x="concept-idl-convert">converted</span> to a
-   Web IDL callback type, the <span>incumbent settings object</span> is that corresponding to <code
-   data-x="">window</code> (in the same manner as in our starter example above). Web IDL stores this
-   as the resulting callback value's <span>callback context</span>.</p>
+   Web IDL callback type, the <span data-x="concept-incumbent-realm">incumbent realm</span> is that
+   corresponding to <code data-x="">window</code> (in the same manner as in our starter example
+   above). Web IDL stores this as the resulting callback value's <span>callback context</span>.</p>
 
    <p>When the <span data-x="concept-task">task</span> posted by <code
    data-x="dom-setTimeout">setTimeout()</code> executes, the algorithm for that task uses Web IDL to
    <span data-x="es-invoking-callback-functions">invoke</span> the stored callback value. Web IDL in
    turn calls the above <span>prepare to run a callback</span> algorithm. This pushes the stored
-   <span>callback context</span> onto the <span>backup incumbent settings object stack</span>. At
+   <span>callback context</span> onto the <span>backup incumbent realm stack</span>. At
    this time (inside the timer task) there is no author code on the stack, so the <span>topmost
    script-having execution context</span> is null, and nothing gets its
    <span>skip-when-determining-incumbent counter</span> incremented.</p>
@@ -106950,11 +106947,12 @@ new PaymentRequest(&hellip;); // Allowed to use
    data-x="dom-window-postMessage">postMessage()</code>, with no <span
    data-x="js-ScriptEvaluation">ScriptEvaluation</span> context or similar below it.</p>
 
-   <p>This is where we fall back to the <span>backup incumbent settings object stack</span>. As
-   noted above, it will contain as its topmost entry the <span>relevant settings object</span> of
-   <code data-x="">window</code>. So that is what is used as the <span>incumbent settings
-   object</span> while executing the <code data-x="dom-window-postMessage">postMessage()</code>
-   algorithm.</p>
+   <p>This is where we fall back to the <span>backup incumbent realm stack</span>.
+   As noted above, it will contain as its topmost entry the <span
+   data-x="concept-relevant-realm">relevant realm</span> of <code data-x="">window</code>.
+   So its <span data-x="concept-realm-settings-object">settings object</span> is what is used as the
+   <span>incumbent settings object</span> while executing the <code
+   data-x="dom-window-postMessage">postMessage()</code> algorithm.</p>
   </div>
 
   <div class="example" id="example-incumbent-3">
@@ -106979,21 +106977,21 @@ document.querySelector("button").addEventListener("click", bound);
   };
 &lt;/script></code></pre>
 
-   <p>Again there are two interesting <span data-x="environment settings object">environment
-   settings objects</span> in play: that of <code data-x="">a.html</code>, and that of <code
-   data-x="">b.html</code>. When the <code data-x="dom-location-assign">location.assign()</code>
-   method triggers the <span><code>Location</code>-object navigate</span> algorithm, what will be
-   the <span>incumbent settings object</span>? As before, it should intuitively be that of <code
-   data-x="">a.html</code>: the <code data-x="event-click">click</code> listener was originally
-   scheduled by <code data-x="">a.html</code>, so even if something involving <code
-   data-x="">b.html</code> causes the listener to fire, the <span
-   data-x="concept-incumbent-everything">incumbent</span> responsible is that of <code
-   data-x="">a.html</code>.</p>
+   <p>Again there are two interesting <span data-x="realm">realms</span> in play: that of
+   <code data-x="">a.html</code>, and that of <code data-x="">b.html</code>.
+   When the <code data-x="dom-location-assign">location.assign()</code> method triggers the
+   <span><code>Location</code>-object navigate</span> algorithm, what will be the <span
+   data-x="concept-incumbent-realm">incumbent realm</span>?
+   As before, it should intuitively be that of <code data-x="">a.html</code>: the <code
+   data-x="event-click">click</code> listener was originally scheduled by <code
+   data-x="">a.html</code>, so even if something involving <code data-x="">b.html</code> causes the
+   listener to fire, the <span data-x="concept-incumbent-everything">incumbent</span> responsible is
+   that of <code data-x="">a.html</code>.</p>
 
    <p>The callback setup is similar to the previous example: when <code data-x="">bound</code> is
-   <span data-x="concept-idl-convert">converted</span> to a Web IDL callback type, the
-   <span>incumbent settings object</span> is that corresponding to <code data-x="">a.html</code>,
-   which is stored as the callback's <span>callback context</span>.</p>
+   <span data-x="concept-idl-convert">converted</span> to a Web IDL callback type, the <span
+   data-x="concept-incumbent-realm">incumbent realm</span> is that corresponding to <code
+   data-x="">a.html</code>, which is stored as the callback's <span>callback context</span>.</p>
 
    <p>When the <code data-x="dom-click">click()</code> method is called inside <code
    data-x="">b.html</code>, it <span data-x="concept-event-dispatch">dispatches</span> a <code
@@ -107002,17 +107000,16 @@ document.querySelector("button").addEventListener("click", bound);
    executes as part of event dispatch, there <em>is</em> author code on the stack; the <span>topmost
    script-having execution context</span> is that of the <code data-x="">onLoad</code> function,
    whose <span>skip-when-determining-incumbent counter</span> gets incremented. Additionally, <code
-   data-x="">a.html</code>'s <span>environment settings object</span> (stored as the
-   <code>EventHandler</code>'s <span>callback context</span>) is pushed onto the
-   <span>backup incumbent settings object stack</span>.</p>
+   data-x="">a.html</code>'s <span>realm</span> (stored as the <code>EventHandler</code>'s
+   <span>callback context</span>) is pushed onto the <span>backup incumbent realm stack</span>.</p>
 
    <p>Now, when the <span><code>Location</code>-object navigate</span> algorithm looks up the
-   <span>incumbent settings object</span>, the <span>topmost script-having execution
-   context</span> is still that of the <code data-x="">onLoad</code> function (due to the fact we
-   are using a bound function as the callback). Its <span>skip-when-determining-incumbent
-   counter</span> value is one, however, so we fall back to the <span>backup incumbent settings
-   object stack</span>. This gives us the <span>environment settings object</span> of <code
-   data-x="">a.html</code>, as expected.</p>
+   <span data-x="concept-incumbent-global">incumbent global object</span>, the <span>topmost
+   script-having execution context</span> is still that of the <code data-x="">onLoad</code>
+   function (due to the fact we are using a bound function as the callback).
+   Its <span>skip-when-determining-incumbent counter</span> value is one, however, so we fall back
+   to the <span>backup incumbent realm stack</span>.
+   This gives us the <span>realm</span> of <code data-x="">a.html</code>, as expected.</p>
 
    <p>Note that this means that even though it is the <code>iframe</code> inside <code
    data-x="">a.html</code> that navigates, it is <code data-x="">a.html</code> itself that is used
@@ -110551,14 +110548,14 @@ dictionary <dfn dictionary>PromiseRejectionEventInit</dfn> : <span>EventInit</sp
   <ref>JAVASCRIPT</ref></p>
 
   <ol>
-   <li><p>Let <var>incumbent settings</var> be
-   <var>callback</var>.[[HostDefined]].[[IncumbentSettings]].</p></li>
+   <li><p>Let <var>incumbent realm</var> be
+   <var>callback</var>.[[HostDefined]].[[IncumbentRealm]].</p></li>
 
    <li><p>Let <var>script execution context</var> be
    <var>callback</var>.[[HostDefined]].[[ActiveScriptContext]].</li>
 
    <li>
-    <p><span>Prepare to run a callback</span> with <var>incumbent settings</var>.</p>
+    <p><span>Prepare to run a callback</span> with <var>incumbent realm</var>.</p>
 
     <p class="note">This affects the <span data-x="concept-incumbent-everything">incumbent</span>
     concept while the callback runs.</p>
@@ -110579,8 +110576,7 @@ dictionary <dfn dictionary>PromiseRejectionEventInit</dfn> : <span>EventInit</sp
    pop">pop</span> <var>script execution context</var> from the <span>JavaScript execution context
    stack</span>.</p></li>
 
-   <li><p><span>Clean up after running a callback</span> with <var>incumbent
-   settings</var>.</p></li>
+   <li><p><span>Clean up after running a callback</span> with <var>incumbent realm</var>.</p></li>
 
    <li><p>Return <var>result</var>.</p></li>
   </ol>
@@ -110770,7 +110766,7 @@ dictionary <dfn dictionary>PromiseRejectionEventInit</dfn> : <span>EventInit</sp
   <ref>JAVASCRIPT</ref></p>
 
   <ol>
-   <li><p>Let <var>incumbent settings</var> be the <span>incumbent settings object</span>.</p></li>
+   <li><p>Let <var>incumbent realm</var> be the <span>incumbent realm</span>.</p></li>
 
    <li><p>Let <var>active script</var> be the <span>active script</span>.</p></li>
 
@@ -110822,7 +110818,7 @@ dictionary <dfn dictionary>PromiseRejectionEventInit</dfn> : <span>EventInit</sp
    </li>
 
    <li><p>Return the <span>JobCallback Record</span> { [[Callback]]: <var>callable</var>,
-   [[HostDefined]]: { [[IncumbentSettings]]: <var>incumbent settings</var>, [[ActiveScriptContext]]:
+   [[HostDefined]]: { [[IncumbentRealm]]: <var>incumbent realm</var>, [[ActiveScriptContext]]:
    <var>script execution context</var> } }.</p></li>
   </ol>