Sync with recent changes to the JS spec's job queue

domenic · domenic · commit 5af258f33e3e · 2016-03-19T19:26:23.000-04:00
In tc39/ecma262@7032383, JS made the first step toward a more usable job queue setup by removing the script/module evaluation from InitializeHostDefinedRealm, and removing the special NextJob algorithm step for terminating jobs. This allows us to stop saying "Do not obtain any source texts for scripts or modules", and to stop overriding NextJob, instead moving the reaction step to our definition of EnqueueJob. As a drive-by fix, consistified HostPromiseRejectionTracker's heading to match those of the other host-defined abstract operations.
diff --git a/source b/source
@@ -3028,13 +3028,13 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
      <li>The <dfn data-noexport="" data-x-href="https://tc39.github.io/ecma262/#sec-ordinaryownpropertykeys">OrdinaryOwnPropertyKeys</dfn> abstract operation</li>
      <li>The <dfn data-noexport="" data-x="js-ParseModule" data-x-href="https://tc39.github.io/ecma262/#sec-parsemodule">ParseModule</dfn> abstract operation</li>
      <li>The <dfn data-noexport="" data-x="js-ParseScript" data-x-href="https://tc39.github.io/ecma262/#sec-parse-script">ParseScript</dfn> abstract operation</li>
+     <li>The <dfn data-noexport="" data-x-href="https://tc39.github.io/ecma262/#sec-runjobs">RunJobs</dfn> abstract operation</li>
      <li>The <dfn data-noexport="" data-x-href="https://tc39.github.io/ecma262/#sec-samevalue">SameValue</dfn> abstract operation</li>
      <li>The <dfn data-noexport="" data-x="js-ScriptEvaluation" data-x-href="https://tc39.github.io/ecma262/#sec-runtime-semantics-scriptevaluation">ScriptEvaluation</dfn> abstract operation</li>
      <li>The <dfn data-noexport="" data-x="js-ToBoolean" data-x-href="https://tc39.github.io/ecma262/#sec-toboolean">ToBoolean</dfn> abstract operation</li>
      <li>The <dfn data-noexport="" data-x-href="https://tc39.github.io/ecma262/#sec-tostring">ToString</dfn> abstract operation</li>
      <li>The <dfn data-noexport="" data-x-href="https://tc39.github.io/ecma262/#sec-touint32">ToUint32</dfn> abstract operation</li>
      <li>The <dfn data-noexport="" data-x-href="https://tc39.github.io/ecma262/#typedarray-create">TypedArrayCreate</dfn> abstract operation</li>
-     <li>The <dfn data-noexport="" data-x="js-NextJob" data-x-href="https://tc39.github.io/ecma262/#sec-nextjob-result">NextJob</dfn> algorithm step
      <li>The <dfn data-noexport="" data-x="js-abstract-equality" data-x-href="https://tc39.github.io/ecma262/#sec-abstract-equality-comparison">Abstract Equality Comparison</dfn> algorithm
      <li>The <dfn data-noexport="" data-x="js-strict-equality" data-x-href="https://tc39.github.io/ecma262/#sec-strict-equality-comparison">Strict Equality Comparison</dfn> algorithm
      <li>The <dfn data-noexport="" data-x-href="https://tc39.github.io/ecma262/#sec-date-objects"><code>Date</code></dfn> class
@@ -75977,8 +75977,6 @@ dictionary <dfn>DragEventInit</dfn> : <span>MouseEventInit</span> {
 
      <li><p>Let <var>realm execution context</var> be the created <span>JavaScript execution
      context</span>.</p></li>
-
-     <li><p>Do not obtain any source texts for scripts or modules.</p></li>
     </ul>
    </li>
 
@@ -85693,22 +85691,24 @@ interface <dfn>NavigatorOnLine</dfn> {
   <p>The JavaScript specification defines the JavaScript job and job queue abstractions in order to
   specify certain invariants about how promise operations execute with a clean <span>JavaScript
   execution context stack</span> and in a certain order. However, as of the time of this writing
-  the definitions of <span data-x="js-EnqueueJob">EnqueueJob</span> and <span
-  data-x="js-NextJob">NextJob</span> in that specification are not sufficiently flexible to
-  integrate with HTML as a host environment. <ref spec="ECMA262"></p>
+  the definition of <span data-x="js-EnqueueJob">EnqueueJob</span> in that specification is not
+  sufficiently flexible to integrate with HTML as a host environment. <ref spec="ECMA262"></p>
 
   <p class="note">This is not strictly true. It is in fact possible, by taking liberal advantage of
-  the many "implementation defined" sections of those algorithms, to contort them to our purposes.
+  the many "implementation defined" sections of the algorithm, to contort it to our purposes.
   However, the end result is a mass of messy indirection and workarounds that essentially bypasses
   the job queue infrastructure entirely, albeit in a way that is technically sanctioned within the
   bounds of implementation-defined behavior. We do not take this path, and instead introduce the
-  following <span data-x="willful violation">willful violations</span>.</p>
+  following <span>willful violation</span>.</p>
 
-  <p>As such, user agents must instead use the following definitions in place of those in the
+  <p>As such, user agents must instead use the following definition in place of that in the
   JavaScript specification. These ensure that the promise jobs enqueued by the JavaScript
   specification are properly integrated into the user agent's <span data-x="event loop">event
   loops</span>.</p>
 
+  <p>The <span>RunJobs</span> abstract operation from the JavaScript specification must
+  not be used by user agents.</p>
+
   <h6><dfn>EnqueueJob</dfn>(<var>queueName</var>, <var>job</var>, <var>arguments</var>)</h6>
 
   <p>When the JavaScript specification says to call the EnqueueJob abstract operation, the
@@ -85728,28 +85728,15 @@ interface <dfn>NavigatorOnLine</dfn> {
      <li><p><span>Check if we can run script</span> with <var>settings</var>. If this returns "do
      not run" then abort these steps.</p></li>
      <li><p><span>Prepare to run script</span> with <var>settings</var>.</p></li>
-     <li><p>Perform the abstract operation specified by <var>job</var>, using the elements of
-     <var>arguments</var> as its arguments.</p></li>
+     <li><p>Let <var>result</var> be the result of performing the abstract operation specified by
+     <var>job</var>, using the elements of <var>arguments</var> as its arguments.</p></li>
      <li><p><span>Clean up after running script</span> with <var>settings</var>.</p></li>
+     <li><p>If <var>result</var> is an abrupt completion, <span>report the exception</span> given by
+     <var>result</var>.[[Value]].</p></li>
     </ol>
    </li>
   </ol>
 
-  <h6><dfn>NextJob</dfn> <var>result</var></h6>
-
-  <p>When the JavaScript specification uses the algorithm step NextJob, the following steps must be
-  used in place of those specified by JavaScript's <span data-x="js-NextJob">NextJob</span>:</p>
-
-  <ol>
-   <li><p>If <var>result</var> is an abrupt completion, <span>report the exception</span> given by
-   <var>result</var>.[[Value]].</p></li>
-  </ol>
-
-  <p class="note">A more accurate name for our overridden version of NextJob would be along the
-  lines of "yield to host environment" or "allow host environment to react to job results". The
-  process of actually initiating the next job will be taken care of by the <span>event
-  loop</span>.</p>
-
   <h5>Integration with the JavaScript module system</h5>
 
   <p>The JavaScript specification defines a syntax for modules, as well as some host-agnostic parts
@@ -85792,7 +85779,7 @@ interface <dfn>NavigatorOnLine</dfn> {
 
   <p>JavaScript contains an implementation-defined <span
   data-x="js-HostResolveImportedModule">HostResolveImportedModule</span> abstract operation. User
-  agents must use the following implementation. <ref spec="ECMA262"></p>
+  agents must use the following implementation: <ref spec="ECMA262"></p>
 
   <ol>
    <li><p>Let <var>referencing module script</var> be
@@ -86027,7 +86014,7 @@ dictionary <dfn>ErrorEventInit</dfn> : <span>EventInit</span> {
   be reported to a developer console.</p>
 
 
-  <h6>The HostPromiseRejectionTracker implementation</h6>
+  <h6 id="the-hostpromiserejectiontracker-implementation"><dfn>HostPromiseRejectionTracker</dfn>(<var>promise</var>, <var>operation</var>)</h6>
 
   <p>JavaScript contains an implementation-defined <span
   data-x="js-HostPromiseRejectionTracker">HostPromiseRejectionTracker</span>(<var>promise</var>,
@@ -87789,8 +87776,6 @@ interface <dfn>WindowBase64</dfn> {
 
      <li><p>Let <var>realm execution context</var> be the created <span>JavaScript execution
      context</span>.</p></li>
-
-     <li><p>Do not obtain any source texts for scripts or modules.</p></li>
     </ul>
    </li>
 
@@ -94552,8 +94537,6 @@ interface <dfn>WorkerGlobalScope</dfn> : <span>EventTarget</span> {
 
      <li><p>Let <var>realm execution context</var> be the created <span>JavaScript execution
      context</span>.</p></li>
-
-     <li><p>Do not obtain any source texts for scripts or modules.</p></li>
     </ul>
    </li>
 
