Meta: export various terms used by Service Workers

Co-authored-by: Domenic Denicola <d@domenic.me>

Author: jakearchibald

source

@@ -88578,11 +88578,11 @@ interface <dfn interface>BeforeUnloadEvent</dfn> : <span>Event</span> {
   <span>navigable</span>'s <span data-x="nav-active-history-entry">active history entry</span> can
   change synchronously, the new entry will always have the same <code>Document</code>.</p>
 
-  <p>A <span>navigable</span>'s <dfn data-x="nav-bc">active browsing context</dfn> is its <span
-  data-x="nav-document">active document</span>'s <span data-x="concept-document-bc">browsing
-  context</span>. If this <span>navigable</span> is a <span>traversable navigable</span>, then its
-  <span data-x="nav-bc">active browsing context</span> will be a <span>top-level browsing
-  context</span>.</p>
+  <p>A <span>navigable</span>'s <dfn export for="navigable" data-x="nav-bc">active browsing
+  context</dfn> is its <span data-x="nav-document">active document</span>'s <span
+  data-x="concept-document-bc">browsing context</span>. If this <span>navigable</span> is a
+  <span>traversable navigable</span>, then its <span data-x="nav-bc">active browsing context</span>
+  will be a <span>top-level browsing context</span>.</p>
 
   <p>A <span>navigable</span>'s <dfn data-x="nav-wp">active <code>WindowProxy</code></dfn> is its
   <span data-x="nav-bc">active browsing context</span>'s associated <code>WindowProxy</code>.</p>
@@ -96876,7 +96876,8 @@ new PaymentRequest(&hellip;); // Allowed to use
   <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>incumbent settings object</dfn> is determined as follows:</p>
+  <p>With all this in place, the <dfn export>incumbent settings object</dfn> is determined as
+  follows:</p>
 
   <ol>
    <li><p>Let <var>context</var> be the <span>topmost script-having execution
@@ -96910,12 +96911,12 @@ new PaymentRequest(&hellip;); // Allowed to use
    data-x="concept-realm-settings-object">settings object</span>.</p></li>
   </ol>
 
-  <p>Then, the <dfn data-x="concept-incumbent-realm">incumbent realm</dfn> is the <span
+  <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>Similarly, the <dfn 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
+  <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
   settings object</span>.</p>
 
   <hr>
@@ -98679,11 +98680,12 @@ document.querySelector("button").addEventListener("click", bound);
   <h5>Killing scripts</h5>
 
   <p>Although the JavaScript specification does not account for this possibility, it's sometimes
-  necessary to <dfn>abort a running script</dfn>. This causes any <span
-  data-x="js-ScriptEvaluation">ScriptEvaluation</span> or <span>Source Text Module Record</span>
-  <span data-x="js-Evaluate">Evaluate</span> invocations to cease immediately, emptying the
-  <span>JavaScript execution context stack</span> without triggering any of the normal mechanisms
-  like <code data-x="">finally</code> blocks. <ref spec=JAVASCRIPT></p>
+  necessary to <dfn data-lt="abort a running script|abort the running script" export>abort a
+  running script</dfn>. This causes any <span data-x="js-ScriptEvaluation">ScriptEvaluation</span>
+  or <span>Source Text Module Record</span> <span data-x="js-Evaluate">Evaluate</span> invocations
+  to cease immediately, emptying the <span>JavaScript execution context stack</span> without
+  triggering any of the normal mechanisms like <code data-x="">finally</code> blocks. <ref
+  spec=JAVASCRIPT></p>
 
   <p>User agents may impose resource limitations on scripts, for example CPU quotas, memory limits,
   total execution time limits, or bandwidth limitations. When a script exceeds a limit, the user
@@ -103544,11 +103546,11 @@ enum <dfn enum>DOMParserSupportedType</dfn> {
 
   <div w-nodev>
 
-  <p>Objects that implement the <code>WindowOrWorkerGlobalScope</code> mixin have a <dfn>map of
-  active timers</dfn>, which is a <span>map</span>, initially empty. Each <span data-x="map
-  key">key</span> in this map is an identifier for a timer, and each <span data-x="map
-  value">value</span> is a <code>DOMHighResTimeStamp</code>, representing the expiry time for that
-  timer.</p>
+  <p>Objects that implement the <code>WindowOrWorkerGlobalScope</code> mixin have a <dfn export
+  for="WindowOrWorkerGlobalScope">map of active timers</dfn>, which is a <span>map</span>,
+  initially empty. Each <span data-x="map key">key</span> in this map is an identifier for a timer,
+  and each <span data-x="map value">value</span> is a <code>DOMHighResTimeStamp</code>,
+  representing the expiry time for that timer.</p>
 
   <p class="note">For entries put in the <span>map of active timers</span> by the <span>timer
   initialization steps</span>, i.e., by <code data-x="dom-setTimeout">setTimeout()</code> and <code
@@ -108097,7 +108099,7 @@ function showLogout() {
 
 
 
-  <h2 split-filename="workers" id="workers" dfn data-lt="web worker">Web workers</h2>
+  <h2 split-filename="workers" id="workers" dfn data-lt="web worker" export>Web workers</h2>
 
   <h3>Introduction</h3>