From fedaaea0c0ef73eb976cab97c7c94fa0f798af73 Mon Sep 17 00:00:00 2001
From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 2 Mar 2016 13:13:21 +0100
Subject: [PATCH] Use JAVASCRIPT rather than ECMA262 as reference name
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Also reference https://javascript.spec.whatwg.org/ normatively for as
long as it’s still relevant and require it to be implemented.
---
 source | 40 ++++++++++++++++++++++------------------
 1 file changed, 22 insertions(+), 18 deletions(-)

diff --git a/source b/source
index fb2ddc5c9a6..55918b79c31 100644
--- a/source
+++ b/source
@@ -2950,15 +2950,18 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
    <dd>
 
     <p>Some parts of the language described by this specification only support JavaScript as the
-    underlying scripting language. <ref spec=ECMA262></p>
+    underlying scripting language. <ref spec=JAVASCRIPT></p>
 
-    <p class="note">The term "JavaScript" is used to refer to ECMA262, rather than the official term
-    ECMAScript, since the term JavaScript is more widely known. Similarly, the <span>MIME
+    <p class="note">The term "JavaScript" is used to refer to ECMA-262, rather than the official
+    term ECMAScript, since the term JavaScript is more widely known. Similarly, the <span>MIME
     type</span> used to refer to JavaScript in this specification is <code
     data-x="">text/javascript</code>, since that is the most commonly used type, <span
     data-x="willful violation">despite it being an officially obsoleted type</span> according to RFC
     4329. <ref spec=RFC4329></p>
 
+    <p>User agents must follow the additions and clarifications made in the WHATWG JavaScript
+    standard. <ref spec=JAVASCRIPT></p>
+
     <p>The following terms are defined in the JavaScript specification and used in this specification:</p>
 
     <ul class="brief">
@@ -7866,7 +7869,7 @@ interface <dfn>DOMStringMap</dfn> {
   <h3>Safe passing of structured data</h3>
 
   <p>This section uses the terminology and typographic conventions from the JavaScript
-  specification. <ref spec=ECMA262></p>
+  specification. <ref spec=JAVASCRIPT></p>
 
   <h4><dfn>Cloneable objects</dfn></h4>
 
@@ -7976,7 +7979,7 @@ interface <dfn>DOMStringMap</dfn> {
       <var>placeholderResult</var>, now holds a reference to <var>transferResult</var>.</p>
 
       <p class="note">This is a rather unusual low-level operation for which no primitives are
-      defined by ECMAScript.</p>
+      defined by JavaScript.</p>
      </li>
 
      <li><p>Add <var>transferResult</var> as the last element of
@@ -15716,7 +15719,7 @@ Space is not the only void</pre>
 
    <p>The following JavaScript function shows how the tree walk could be implemented. The <var>root</var> argument is the root of the tree to walk (either a <span>sectioning
    content</span> element or a <span>sectioning root</span> element), and the <var>enter</var> and <var>exit</var> arguments are callbacks that are called with
-   the nodes as they are entered and exited. <ref spec=ECMA262></p>
+   the nodes as they are entered and exited. <ref spec=JAVASCRIPT></p>
 
    <pre>function (root, enter, exit) {
   var node = root;
@@ -47414,7 +47417,7 @@ ldh-str       = &lt; as defined in <a href="https://tools.ietf.org/html/rfc1034#
   with only the "<code data-x="">u</code>" flag specified, compiles successfully, then the resulting regular expression is the element's
   <dfn>compiled pattern regular expression</dfn>. If the element has no such attribute, or if the
   value doesn't compile successfully, then the element has no <span>compiled pattern regular
-  expression</span>. <ref spec=ECMA262></p>
+  expression</span>. <ref spec=JAVASCRIPT></p>
 
   <p class="note">If the value doesn't compile successfully, user agents are encouraged to log this
   fact in a developer console, to aid debugging.</p>
@@ -57956,7 +57959,7 @@ dictionary <dfn>RelatedEventInit</dfn> : <span>EventInit</span> {
   with the requirements of the JavaScript specification's <i data-x="js-prod-Script">Script</i> or
   <i data-x="js-prod-Module">Module</i> productions, for <span data-x="classic script">classic
   scripts</span> and <span data-x="module script">module scripts</span> respectively. <ref
-  spec="ECMA262"></p>
+  spec="JAVASCRIPT"></p>
 
   <p>When used to include <span data-x="data block">data blocks</span>, the data must be embedded
   inline, the format of the data must be given using the <code
@@ -58928,7 +58931,7 @@ o............A....e
   <h5 id="scriptingLanguages">Scripting languages</h5>
 
   <p>A <dfn>JavaScript MIME type</dfn> is a <span>MIME type</span> string that is one of the
-  following and refers to JavaScript: <ref spec=ECMA262></p>
+  following and refers to JavaScript: <ref spec=JAVASCRIPT></p>
 
   <ul class="brief">
    <li><code>application/ecmascript</code>
@@ -85671,7 +85674,7 @@ interface <dfn>NavigatorOnLine</dfn> {
   data-x="js-ScriptEvaluation">ScriptEvaluation</span> or <span
   data-x="js-ModuleEvaluation">ModuleEvaluation</span> 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=ECMA262></p>
+  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
@@ -85710,7 +85713,7 @@ interface <dfn>NavigatorOnLine</dfn> {
   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 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>
+  sufficiently flexible to integrate with HTML as a host environment. <ref spec=JAVASCRIPT></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 the algorithm, to contort it to our purposes.
@@ -85760,7 +85763,7 @@ interface <dfn>NavigatorOnLine</dfn> {
   of their processing model. This specification defines the rest of their processing model: how the
   module system is bootstrapped, via the <code>script</code> element with <code
   data-x="attr-script-type">type</code> attribute set to "<code data-x="">module</code>", and how
-  modules are fetched, resolved, and executed. <ref spec="ECMA262"></p>
+  modules are fetched, resolved, and executed. <ref spec="JAVASCRIPT"></p>
 
   <p class="note">Although the JavaScript specification speaks in terms of "scripts" versus
   "modules", in general this specification speaks in terms of <span data-x="classic script">classic
@@ -85802,7 +85805,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=JAVASCRIPT></p>
 
   <ol>
    <li><p>Let <var>referencing module script</var> be
@@ -86040,7 +86043,7 @@ dictionary <dfn>ErrorEventInit</dfn> : <span>EventInit</span> {
   <p>JavaScript contains an implementation-defined <span
   data-x="js-HostPromiseRejectionTracker">HostPromiseRejectionTracker</span>(<var>promise</var>,
   <var>operation</var>) abstract operation. User agents must use the following implementation:
-  <ref spec=ECMA262></p>
+  <ref spec=JAVASCRIPT></p>
 
   <ol>
 
@@ -111363,7 +111366,7 @@ if (s = prompt('What is your name?')) {
   legacy content: one that uses the presence of <code data-x="dom-document-all">document.all</code>
   as a way to detect legacy user agents, and one that only supports those legacy user agents and
   uses the <code data-x="dom-document-all">document.all</code> object without testing for its
-  presence first. <ref spec=ECMA262></p>
+  presence first. <ref spec=JAVASCRIPT></p>
 
   <hr>
 
@@ -116706,9 +116709,6 @@ INSERT INTERFACES HERE
    <dt id="refsE163">[E163]</dt>
    <dd><cite>Recommendation E.163 &mdash; Numbering Plan for The International Telephone Service</cite>, CCITT Blue Book, Fascicle II.2, pp. 128-134, November 1988.</dd>
 
-   <dt id="refsECMA262">[ECMA262]</dt>
-   <dd><cite><a href="https://tc39.github.io/ecma262/">ECMAScript Language Specification</a></cite>. Ecma International.</dd>
-
    <dt id="refsEDITING">[EDITING]</dt>
    <dd><cite><a href="https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html">HTML Editing APIs</a></cite>, A. Gregor. W3C Editing APIs CG.</dd>
 
@@ -116778,6 +116778,10 @@ INSERT INTERFACES HERE
    <dt id="refsISO8601">[ISO8601]</dt>
    <dd>(Non-normative) <cite><a href="http://isotc.iso.org/livelink/livelink/4021199/ISO_8601_2004_E.zip?func=doc.Fetch&amp;nodeid=4021199">ISO8601: Data elements and interchange formats &mdash; Information interchange &mdash; Representation of dates and times</a></cite>. ISO.</dd>
 
+   <dt id="refsJAVASCRIPT">[JAVASCRIPT]</dt>
+   <dd><cite><a href="https://tc39.github.io/ecma262/">ECMAScript Language Specification</a></cite>. Ecma International.</dd>
+   <dd><cite><a href="https://javascript.spec.whatwg.org/">JavaScript Standard</a></cite>, M. Bynens. WHATWG.</dd>
+
    <dt id="refsJLREQ">[JLREQ]</dt>
    <dd><cite><a href="https://www.w3.org/TR/jlreq/">Requirements for Japanese Text Layout</a></cite>. W3C.</dd> <!-- too many editors to list -->