Editorial: export more definitions for Bikeshed-using specs

jyasskin · domenic · commit 81ee034f316f · 2016-08-26T16:15:45.000-04:00
In particular, this takes care of the terms that Bluetooth and
Permissions use.
diff --git a/source b/source
@@ -2015,13 +2015,13 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
 
   <p>When an algorithm B says to return to another algorithm A, it implies that A called B. Upon
   returning to A, the implementation must continue from where it left off in calling B. Some
-  algorithms run <dfn>in parallel</dfn>; this means that the algorithm's subsequent steps are to be
-  run, one after another, at the same time as other logic in the specification (e.g. at the same
-  time as the <span>event loop</span>). This specification does not define the precise mechanism by
-  which this is achieved, be it time-sharing cooperative multitasking, fibers, threads, processes,
-  using different hyperthreads, cores, CPUs, machines, etc. By contrast, an operation that is to run
-  <dfn>immediately</dfn> must interrupt the currently running task, run itself, and then resume the
-  previously running task.</p>
+  algorithms run <dfn data-export="">in parallel</dfn>; this means that the algorithm's subsequent
+  steps are to be run, one after another, at the same time as other logic in the specification (e.g.
+  at the same time as the <span>event loop</span>). This specification does not define the precise
+  mechanism by which this is achieved, be it time-sharing cooperative multitasking, fibers, threads,
+  processes, using different hyperthreads, cores, CPUs, machines, etc. By contrast, an operation
+  that is to run <dfn>immediately</dfn> must interrupt the currently running task, run itself, and
+  then resume the previously running task.</p>
 
   </div>
 
@@ -28618,8 +28618,8 @@ interface <dfn>HTMLIFrameElement</dfn> : <span>HTMLElement</span> {
 
   <div w-nodev>
    <p id="fullscreen-logic">To determine whether a <code>Document</code> object <var>document</var>
-   is <dfn>allowed to use</dfn> the feature indicated by attribute name <var>allowattribute</var>,
-   run these steps:</p>
+   is <dfn data-export="">allowed to use</dfn> the feature indicated by attribute name
+   <var>allowattribute</var>, run these steps:</p>
 
    <ol>
     <li><p>If <var>document</var> has no <span data-x="concept-document-bc">browsing context</span>,
@@ -72266,8 +72266,8 @@ END:VCARD</pre>
   refer to the <code data-x="event-click">click</code> event that was fired by the steps above
   leading up to this point.</p>
 
-  <p id="allowed-to-show-a-popup">An algorithm is <dfn>triggered by user activation</dfn> if any of
-  the following conditions is true:</p>
+  <p id="allowed-to-show-a-popup">An algorithm is <dfn data-export="">triggered by user
+  activation</dfn> if any of the following conditions is true:</p>
 
   <ul>
    <li><p>The <span data-x="concept-task">task</span> in which the algorithm is running is currently
@@ -81711,9 +81711,9 @@ State: &lt;OUTPUT NAME=I>1&lt;/OUTPUT> &lt;INPUT VALUE="Increment" TYPE=BUTTON O
   <!-- NAVIGATE <dfn>navigate</dfn> -->
   <!-- For places that _call_ this, as opposed to just referring to
   it, search for "DONAV" -->
-  <p>To <dfn>navigate</dfn> a browsing context <var>browsingContext</var> to a resource
-  <var>resource</var>, optionally with an <dfn id="exceptions-enabled"><var>exceptions enabled
-  flag</var></dfn>, the user agent must run these steps:</p>
+  <p>To <dfn data-export="">navigate</dfn> a browsing context <var>browsingContext</var> to a
+  resource <var>resource</var>, optionally with an <dfn id="exceptions-enabled"><var>exceptions
+  enabled flag</var></dfn>, the user agent must run these steps:</p>
 
   <ol>
    <li><p>If <var>resource</var> is a <span>URL</span>, then set <var>resource</var> to a new <span
@@ -88178,8 +88178,9 @@ dictionary <dfn>PromiseRejectionEventInit</dfn> : <span>EventInit</span> {
   <span data-x="concept-task">task</span>'s associated <code>Document</code> or <a
   href="#workers">worker</a>.</p>
 
-  <p>When a user agent is to <dfn>queue a task</dfn>, it must add the given task to one of the <span
-  data-x="task queue">task queues</span> of the relevant <span>event loop</span>.</p>
+  <p>When a user agent is to <dfn data-export="">queue a task</dfn>, it must add the given task to
+  one of the <span data-x="task queue">task queues</span> of the relevant <span>event
+  loop</span>.</p>
 
   <p>Each <span data-x="concept-task">task</span> is defined as coming from a specific <dfn>task
   source</dfn>. All the tasks from one particular <span>task source</span> and destined to a
@@ -88393,8 +88394,9 @@ dictionary <dfn>PromiseRejectionEventInit</dfn> : <span>EventInit</span> {
   source</span> used. Normally, the <span>task source</span> of a <span>microtask</span> is
   irrelevant.</p>
 
-  <p>When a user agent is to <dfn>perform a microtask checkpoint</dfn>, if the <span>performing a
-  microtask checkpoint</span> flag is false, then the user agent must run the following steps:</p>
+  <p>When a user agent is to <dfn data-export="">perform a microtask checkpoint</dfn>, if the
+  <span>performing a microtask checkpoint</span> flag is false, then the user agent must run the
+  following steps:</p>
 
   <ol>
 
@@ -88627,8 +88629,8 @@ dictionary <dfn>PromiseRejectionEventInit</dfn> : <span>EventInit</span> {
 
   <!--test: <a href="http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A...%3Cscript%3E%0Aw(a%3Ddocument.implementation.createDocument(null%2C%20null%2C%20null))%3B%0Aw(a.appendChild(a.createElementNS('http%3A%2F%2Fwww.w3.org%2F1999%2Fxhtml'%2C%20'html')))%3B%0Aw(b%3Da.firstChild.appendChild(a.createElementNS('http%3A%2F%2Fwww.w3.org%2F1999%2Fxhtml'%2C%20'body')))%3B%0Aw(b.test%20%3D%20w)%3B%0Aw(b.setAttribute('onclick'%2C%20'test(%22fire%3A%20%22%20%2B%20event)'))%3B%0Aw(b.onclick)%3B%0Aw(e%3Da.createEvent('Event'))%3B%0Aw(e.initEvent('click'%2C%20false%2C%20false))%3B%0Aw(b.dispatchEvent(e))%3B%0A%3C%2Fscript%3E">test</a>-->
 
-  <p>Many objects can have <dfn>event handlers</dfn> specified. These act as non-capture event
-  listeners for the object on which they are specified. <ref spec=DOM></p>
+  <p>Many objects can have <dfn data-export="">event handlers</dfn> specified. These act as
+  non-capture event listeners for the object on which they are specified. <ref spec=DOM></p>
 
   <p>An <span data-x="event handlers">event handler</span> has a name, which always starts with
   "<code data-x="">on</code>" and is followed by the name of the event for which it is intended.</p>
@@ -88717,9 +88719,9 @@ dictionary <dfn>PromiseRejectionEventInit</dfn> : <span>EventInit</span> {
   or object <var>T</var> implementing the <code>EventTarget</code> interface is first set
   to a non-null value, the user agent must append an <span data-x="concept-event-listener">event
   listener</span> to the list of <span data-x="concept-event-listener">event listeners</span>
-  associated with <var>T</var> with <b>type</b> set to the <dfn>event handler event type</dfn>
-  corresponding to <var>H</var> and <b>callback</b> set to <span>the event handler processing
-  algorithm</span> defined below. <ref spec=DOM></p>
+  associated with <var>T</var> with <b>type</b> set to the <dfn data-export="">event handler event
+  type</dfn> corresponding to <var>H</var> and <b>callback</b> set to <span>the event handler
+  processing algorithm</span> defined below. <ref spec=DOM></p>
 
   <p class="note">The <b>callback</b> is emphatically <em>not</em> the <span data-x="event
   handlers">event handler</span> itself. Every event handler ends up registering the same
