Update gh-pages

tc39 · Feb 27, 2025 · 80e3cad · 80e3cad
1 parent 6e38781
commit 80e3cad
Show file tree

Hide file tree

Showing 42 changed files with 19,728 additions and 19,728 deletions.
diff --git a/assets/ecmarkup.js b/assets/ecmarkup.js
diff --git a/assets/multipage.js b/assets/multipage.js
diff --git a/index.html b/index.html
diff --git a/multipage/abstract-operations.html b/multipage/abstract-operations.html
diff --git a/multipage/additional-ecmascript-features-for-web-browsers.html b/multipage/additional-ecmascript-features-for-web-browsers.html
diff --git a/multipage/additions-and-changes-that-introduce-incompatibilities-with-prior-editions.html b/multipage/additions-and-changes-that-introduce-incompatibilities-with-prior-editions.html
diff --git a/multipage/bibliography.html b/multipage/bibliography.html
@@ -50,7 +50,7 @@
     right: 1em;
   }
 </style>
-<title>ECMAScript® 2025 Language&nbsp;Specification</title><script src="../assets/multipage.js?cache=g6VYXnvP" defer=""></script><script src="../assets/ecmarkup.js?cache=Dzi6RyfX" defer=""></script><style>
+<title>ECMAScript® 2025 Language&nbsp;Specification</title><script src="../assets/multipage.js?cache=2pYgzwpe" defer=""></script><script src="../assets/ecmarkup.js?cache=Va6Io9jb" defer=""></script><style>
     @media print {
       @page :left {
         @bottom-right {

diff --git a/multipage/colophon.html b/multipage/colophon.html
@@ -50,7 +50,7 @@
     right: 1em;
   }
 </style>
-<title>ECMAScript® 2025 Language&nbsp;Specification</title><script src="../assets/multipage.js?cache=g6VYXnvP" defer=""></script><script src="../assets/ecmarkup.js?cache=Dzi6RyfX" defer=""></script><style>
+<title>ECMAScript® 2025 Language&nbsp;Specification</title><script src="../assets/multipage.js?cache=2pYgzwpe" defer=""></script><script src="../assets/ecmarkup.js?cache=Va6Io9jb" defer=""></script><style>
     @media print {
       @page :left {
         @bottom-right {

diff --git a/multipage/conformance.html b/multipage/conformance.html
@@ -50,7 +50,7 @@
     right: 1em;
   }
 </style>
-<title>ECMAScript® 2025 Language&nbsp;Specification</title><script src="../assets/multipage.js?cache=g6VYXnvP" defer=""></script><script src="../assets/ecmarkup.js?cache=Dzi6RyfX" defer=""></script><style>
+<title>ECMAScript® 2025 Language&nbsp;Specification</title><script src="../assets/multipage.js?cache=2pYgzwpe" defer=""></script><script src="../assets/ecmarkup.js?cache=Va6Io9jb" defer=""></script><style>
     @media print {
       @page :left {
         @bottom-right {
@@ -100,23 +100,23 @@ <h1><span class="secnum">2</span> Conformance</h1>
   <p>A conforming implementation of ECMAScript must interpret source text input in conformance with the latest version of the Unicode Standard and ISO/IEC 10646.</p>
   <p>A conforming implementation of ECMAScript that provides an application programming interface (API) that supports programs that need to adapt to the linguistic and cultural conventions used by different human languages and countries must implement the interface defined by the most recent edition of ECMA-402 that is compatible with this specification.</p>
   <p>A conforming implementation of ECMAScript may provide additional types, values, objects, properties, and functions beyond those described in this specification. In particular, a conforming implementation of ECMAScript may provide properties not described in this specification, and values for those properties, for objects that are described in this specification.</p>
-  <p>A conforming implementation of ECMAScript may support program and regular expression syntax not described in this specification. In particular, a conforming implementation of ECMAScript may support program syntax that makes use of any “future <emu-xref href="#sec-keywords-and-reserved-words" id="_ref_998"><a href="ecmascript-language-lexical-grammar.html#sec-keywords-and-reserved-words">reserved words</a></emu-xref>” noted in subclause <emu-xref href="#sec-keywords-and-reserved-words" id="_ref_1"><a href="ecmascript-language-lexical-grammar.html#sec-keywords-and-reserved-words">12.7.2</a></emu-xref> of this specification.</p>
+  <p>A conforming implementation of ECMAScript may support program and regular expression syntax not described in this specification. In particular, a conforming implementation of ECMAScript may support program syntax that makes use of any “future <emu-xref href="#sec-keywords-and-reserved-words" id="_ref_999"><a href="ecmascript-language-lexical-grammar.html#sec-keywords-and-reserved-words">reserved words</a></emu-xref>” noted in subclause <emu-xref href="#sec-keywords-and-reserved-words" id="_ref_1"><a href="ecmascript-language-lexical-grammar.html#sec-keywords-and-reserved-words">12.7.2</a></emu-xref> of this specification.</p>
   <p>A conforming implementation of ECMAScript must not implement any extension that is listed as a Forbidden Extension in subclause <emu-xref href="#sec-forbidden-extensions" id="_ref_2"><a href="error-handling-and-language-extensions.html#sec-forbidden-extensions">17.1</a></emu-xref>.</p>
-  <p>A conforming implementation of ECMAScript must not redefine any facilities that are not <emu-xref href="#implementation-defined" id="_ref_999"><a href="overview.html#implementation-defined">implementation-defined</a></emu-xref>, <emu-xref href="#implementation-approximated" id="_ref_1000"><a href="overview.html#implementation-approximated">implementation-approximated</a></emu-xref>, or <emu-xref href="#host-defined" id="_ref_1001"><a href="overview.html#host-defined">host-defined</a></emu-xref>.</p>
+  <p>A conforming implementation of ECMAScript must not redefine any facilities that are not <emu-xref href="#implementation-defined" id="_ref_1000"><a href="overview.html#implementation-defined">implementation-defined</a></emu-xref>, <emu-xref href="#implementation-approximated" id="_ref_1001"><a href="overview.html#implementation-approximated">implementation-approximated</a></emu-xref>, or <emu-xref href="#host-defined" id="_ref_1002"><a href="overview.html#host-defined">host-defined</a></emu-xref>.</p>
   <p>A conforming implementation of ECMAScript may choose to implement or not implement <dfn tabindex="-1">Normative Optional</dfn> subclauses. If any Normative Optional behaviour is implemented, all of the behaviour in the containing Normative Optional clause must be implemented. A Normative Optional clause is denoted in this specification with the words "Normative Optional" in a coloured box, as shown below.</p>
 
-  <emu-clause id="sec-conformance-normative-optional" oldids="sec-conformance.normative-optional" example="" normative-optional=""><div class="attributes-tag"><emu-xref href="#sec-conformance" id="_ref_1002"><a href="conformance.html#sec-conformance">Normative Optional</a></emu-xref></div><span id="sec-conformance.normative-optional"></span>
+  <emu-clause id="sec-conformance-normative-optional" oldids="sec-conformance.normative-optional" example="" normative-optional=""><div class="attributes-tag"><emu-xref href="#sec-conformance" id="_ref_1003"><a href="conformance.html#sec-conformance">Normative Optional</a></emu-xref></div><span id="sec-conformance.normative-optional"></span>
     <h1><span class="secnum">2.1</span> Example Normative Optional Clause Heading</h1>
     <p>Example clause contents.</p>
   </emu-clause>
   <p>A conforming implementation of ECMAScript must implement <dfn tabindex="-1">Legacy</dfn> subclauses, unless they are also marked as Normative Optional. All of the language features and behaviours specified within Legacy subclauses have one or more undesirable characteristics. However, their continued usage in existing applications prevents their removal from this specification. These features are not considered part of the core ECMAScript language. Programmers should not use or assume the existence of these features and behaviours when writing new ECMAScript code.</p>
 
-  <emu-clause id="sec-conformance-legacy" example="" legacy=""><div class="attributes-tag"><emu-xref href="#sec-conformance" id="_ref_1003"><a href="conformance.html#sec-conformance">Legacy</a></emu-xref></div>
+  <emu-clause id="sec-conformance-legacy" example="" legacy=""><div class="attributes-tag"><emu-xref href="#sec-conformance" id="_ref_1004"><a href="conformance.html#sec-conformance">Legacy</a></emu-xref></div>
     <h1><span class="secnum">2.2</span> Example Legacy Clause Heading</h1>
     <p>Example clause contents.</p>
   </emu-clause>
 
-  <emu-clause id="sec-conformance-legacy-normative-optional" example="" legacy="" normative-optional=""><div class="attributes-tag"><emu-xref href="#sec-conformance" id="_ref_1004"><a href="conformance.html#sec-conformance">Normative Optional</a></emu-xref>, <emu-xref href="#sec-conformance" id="_ref_1005"><a href="conformance.html#sec-conformance">Legacy</a></emu-xref></div>
+  <emu-clause id="sec-conformance-legacy-normative-optional" example="" legacy="" normative-optional=""><div class="attributes-tag"><emu-xref href="#sec-conformance" id="_ref_1005"><a href="conformance.html#sec-conformance">Normative Optional</a></emu-xref>, <emu-xref href="#sec-conformance" id="_ref_1006"><a href="conformance.html#sec-conformance">Legacy</a></emu-xref></div>
     <h1><span class="secnum">2.3</span> Example Legacy Normative Optional Clause Heading</h1>
     <p>Example clause contents.</p>
   </emu-clause>