Editorial: Update to ES2026 draft

Co-authored-by: Yuto Yoshino <[email protected]>
Co-authored-by: Richard Gibson <[email protected]>

Author: 3 people

spec/collator.html

@@ -223,7 +223,7 @@ <h1>
           <dd>
             The returned Number represents the result of an implementation-defined locale-sensitive String comparison of _x_ with _y_.
             The result is intended to correspond with a sort order of String values according to the effective locale and collation options of _collator_, and will be negative when _x_ is ordered before _y_, positive when _x_ is ordered after _y_, and zero in all other cases (representing no relative ordering between _x_ and _y_).
-            String values must be interpreted as UTF-16 code unit sequences as described in es2025, <emu-xref href="#sec-ecmascript-language-types-string-type"></emu-xref>, and a surrogate pair (a code unit in the range 0xD800 to 0xDBFF followed by a code unit in the range 0xDC00 to 0xDFFF) within a string must be interpreted as the corresponding code point.
+            String values must be interpreted as UTF-16 code unit sequences as described in es2026, <emu-xref href="#sec-ecmascript-language-types-string-type"></emu-xref>, and a surrogate pair (a code unit in the range 0xD800 to 0xDBFF followed by a code unit in the range 0xDC00 to 0xDFFF) within a string must be interpreted as the corresponding code point.
           </dd>
         </dl>
 

spec/conformance.html

@@ -1,6 +1,6 @@
 <emu-clause id="conformance">
   <h1>Conformance</h1>
-  <p>A conforming implementation of this specification must conform to the ECMAScript 2025 Language Specification (ECMA-262 16<sup>th</sup> Edition, or successor), and must provide and support all the objects, properties, functions, and program semantics described in this specification. Nothing in this specification is intended to allow behaviour that is otherwise prohibited by ECMA-262, and any such conflict should be considered an editorial error rather than an override of constraints from ECMA-262.</p>
+  <p>A conforming implementation of this specification must conform to the ECMAScript 2026 Language Specification (ECMA-262 17<sup>th</sup> Edition, or successor), and must provide and support all the objects, properties, functions, and program semantics described in this specification. Nothing in this specification is intended to allow behaviour that is otherwise prohibited by ECMA-262, and any such conflict should be considered an editorial error rather than an override of constraints from ECMA-262.</p>
   <p>A conforming implementation is permitted to provide additional objects, properties, and functions beyond those described in this specification. In particular, a conforming implementation is permitted to provide properties not described in this specification, and values for those properties, for objects that are described herein. A conforming implementation is not permitted to add optional arguments to the functions defined in this specification.</p>
   <p>A conforming implementation is permitted to accept additional values, and then have implementation-defined behaviour instead of throwing a *RangeError*, for the following properties of _options_ arguments:</p>
   <ul>

spec/conventions.html

@@ -1,13 +1,13 @@
 <emu-clause id="conventions">
   <h1>Notational Conventions</h1>
 
-  <p>This standard uses a subset of the notational conventions of the ECMAScript 2025 Language Specification (ECMA-262 16<sup>th</sup> Edition), as es2025:</p>
+  <p>This standard uses a subset of the notational conventions of the ECMAScript 2026 Language Specification (ECMA-262 17<sup>th</sup> Edition), as es2026:</p>
 
   <ul>
-    <li>Object Internal Methods and Internal Slots, as described in es2025, <emu-xref href="#sec-object-internal-methods-and-internal-slots"></emu-xref>.</li>
-    <li>Algorithm conventions, as described in es2025, <emu-xref href="#sec-algorithm-conventions"></emu-xref>, and the use of abstract operations, as described in es2025, <emu-xref href="#sec-type-conversion"></emu-xref>, <emu-xref href="#sec-testing-and-comparison-operations"></emu-xref>, <emu-xref href="#sec-operations-on-objects"></emu-xref>, <emu-xref href="#sec-operations-on-iterator-objects"></emu-xref>.</li>
-    <li>Internal Slots, as described in es2025, <emu-xref href="#sec-ordinary-object-internal-methods-and-internal-slots"></emu-xref>.</li>
-    <li>The List and Record Specification Type, as described in es2025, <emu-xref href="#sec-list-and-record-specification-type"></emu-xref>.</li>
+    <li>Object Internal Methods and Internal Slots, as described in es2026, <emu-xref href="#sec-object-internal-methods-and-internal-slots"></emu-xref>.</li>
+    <li>Algorithm conventions, as described in es2026, <emu-xref href="#sec-algorithm-conventions"></emu-xref>, and the use of abstract operations, as described in es2026, <emu-xref href="#sec-type-conversion"></emu-xref>, <emu-xref href="#sec-testing-and-comparison-operations"></emu-xref>, <emu-xref href="#sec-operations-on-objects"></emu-xref>, <emu-xref href="#sec-operations-on-iterator-objects"></emu-xref>.</li>
+    <li>Internal Slots, as described in es2026, <emu-xref href="#sec-ordinary-object-internal-methods-and-internal-slots"></emu-xref>.</li>
+    <li>The List and Record Specification Type, as described in es2026, <emu-xref href="#sec-list-and-record-specification-type"></emu-xref>.</li>
   </ul>
 
   <emu-note>
@@ -21,7 +21,7 @@ <h1>Notational Conventions</h1>
   <emu-clause id="sec-402-well-known-intrinsic-objects">
     <h1>Well-Known Intrinsic Objects</h1>
 
-    <p>The following table extends the Well-Known Intrinsic Objects table defined in es2025, <emu-xref href="#sec-well-known-intrinsic-objects"></emu-xref>.</p>
+    <p>The following table extends the Well-Known Intrinsic Objects table defined in es2026, <emu-xref href="#sec-well-known-intrinsic-objects"></emu-xref>.</p>
 
     <emu-table id="table-402-well-known-intrinsic-objects">
       <emu-caption>Well-known Intrinsic Objects (Extensions)</emu-caption>

spec/datetimeformat.html

@@ -1439,7 +1439,7 @@ <h1>
       </h1>
       <dl class="header">
         <dt>description</dt>
-        <dd>It interprets _x_ as a time value as specified in es2025, <emu-xref href="#sec-time-values-and-time-range"></emu-xref>, and creates the corresponding parts according to the effective locale and the formatting options of _dateTimeFormat_.</dd>
+        <dd>It interprets _x_ as a time value as specified in es2026, <emu-xref href="#sec-time-values-and-time-range"></emu-xref>, and creates the corresponding parts according to the effective locale and the formatting options of _dateTimeFormat_.</dd>
       </dl>
       <emu-alg>
         1. Let _x_ be TimeClip(_x_).
@@ -1506,7 +1506,7 @@ <h1>
       </h1>
       <dl class="header">
         <dt>description</dt>
-        <dd>It interprets _x_ and _y_ as time values as specified in es2025, <emu-xref href="#sec-time-values-and-time-range"></emu-xref>, and creates the corresponding parts according to the effective locale and the formatting options of _dateTimeFormat_.</dd>
+        <dd>It interprets _x_ and _y_ as time values as specified in es2026, <emu-xref href="#sec-time-values-and-time-range"></emu-xref>, and creates the corresponding parts according to the effective locale and the formatting options of _dateTimeFormat_.</dd>
       </dl>
       <emu-alg>
         1. Set _x_ to TimeClip(_x_).

spec/index.html

@@ -38,7 +38,7 @@
 }
 </style>
 <pre class="metadata">
-  title: ECMAScript&reg; 2025 Internationalization API Specification
+  title: ECMAScript&reg; 2026 Internationalization API Specification
   shortname: ECMA-402
   status: draft
   location: https://tc39.es/ecma402/

spec/introduction.html

@@ -1,7 +1,7 @@
 <emu-intro id="introduction">
   <h1>Introduction</h1>
   <p>This specification's source can be found at <a href="https://github.com/tc39/ecma402">https://github.com/tc39/ecma402</a>.</p>
-  <p>The ECMAScript 2025 Internationalization API Specification (ECMA-402 12<sup>th</sup> Edition), provides key language sensitive functionality as a complement to the ECMAScript 2025 Language Specification (ECMA-262 16<sup>th</sup> Edition or successor). Its functionality has been selected from that of well-established internationalization APIs such as those of the <dfn id="icu">Internationalization Components for Unicode (ICU) library</dfn> (<a href="https://unicode-org.github.io/icu-docs/">https://unicode-org.github.io/icu-docs/</a>), of the .NET framework, or of the Java platform.</p>
+  <p>The ECMAScript 2026 Internationalization API Specification (ECMA-402 13<sup>th</sup> Edition), provides key language sensitive functionality as a complement to the ECMAScript 2026 Language Specification (ECMA-262 17<sup>th</sup> Edition or successor). Its functionality has been selected from that of well-established internationalization APIs such as those of the <dfn id="icu">Internationalization Components for Unicode (ICU) library</dfn> (<a href="https://unicode-org.github.io/icu-docs/">https://unicode-org.github.io/icu-docs/</a>), of the .NET framework, or of the Java platform.</p>
   <p>The 1<sup>st</sup> Edition API was developed by an ad-hoc group established by Ecma TC39 in September 2010 based on a proposal by Nebojša Ćirić and Jungshik Shin.</p>
   <p>The 2<sup>nd</sup> Edition API was adopted by the General Assembly of June 2015, as a complement to the ECMAScript 6<sup>th</sup> Edition.</p>
   <p>The 3<sup>rd</sup> Edition API was the first edition released under Ecma TC39's new yearly release cadence and open development process. A plain-text source document was built from the ECMA-402 source document to serve as the base for further development entirely on GitHub. Over the year of this standard's development, dozens of pull requests and issues were filed representing several of bug fixes, editorial fixes and other improvements. Additionally, numerous software tools were developed to aid in this effort including Ecmarkup, Ecmarkdown, and Grammarkdown.</p>
@@ -46,4 +46,8 @@ <h1>Introduction</h1>
     Ben Allen, Richard Gibson, Ujjwal Sharma<br>
     ECMA-402, 12<sup>th</sup> Edition Project Editors
   </p>
+  <p>
+    Ben Allen, Richard Gibson, Ujjwal Sharma<br>
+    ECMA-402, 13<sup>th</sup> Edition Project Editors
+  </p>
 </emu-intro>

spec/locale-sensitive-functions.html

@@ -13,7 +13,7 @@ <h1>Properties of the String Prototype Object</h1>
     <emu-clause id="sup-String.prototype.localeCompare">
       <h1>String.prototype.localeCompare ( _that_ [ , _locales_ [ , _options_ ] ] )</h1>
 
-      <p>This definition supersedes the definition provided in es2025, <emu-xref href="#sec-string.prototype.localecompare"></emu-xref>.</p>
+      <p>This definition supersedes the definition provided in es2026, <emu-xref href="#sec-string.prototype.localecompare"></emu-xref>.</p>
 
       <p>When the `localeCompare` method is called with argument _that_ and optional arguments _locales_, and _options_, the following steps are taken:</p>
 
@@ -39,9 +39,9 @@ <h1>String.prototype.localeCompare ( _that_ [ , _locales_ [ , _options_ ] ] )</h
     <emu-clause id="sup-string.prototype.tolocalelowercase">
       <h1>String.prototype.toLocaleLowerCase ( [ _locales_ ] )</h1>
 
-      <p>This definition supersedes the definition provided in es2025, <emu-xref href="#sec-string.prototype.tolocalelowercase"></emu-xref>.</p>
+      <p>This definition supersedes the definition provided in es2026, <emu-xref href="#sec-string.prototype.tolocalelowercase"></emu-xref>.</p>
 
-      <p>This function interprets a String value as a sequence of code points, as described in es2025, <emu-xref href="#sec-ecmascript-language-types-string-type"></emu-xref>. The following steps are taken:</p>
+      <p>This function interprets a String value as a sequence of code points, as described in es2026, <emu-xref href="#sec-ecmascript-language-types-string-type"></emu-xref>. The following steps are taken:</p>
 
       <emu-alg>
         1. Let _O_ be ? RequireObjectCoercible(*this* value).
@@ -63,7 +63,7 @@ <h1>
         </h1>
         <dl class="header">
           <dt>description</dt>
-          <dd>It interprets _S_ as a sequence of UTF-16 encoded code points, as described in es2025, <emu-xref href="#sec-ecmascript-language-types-string-type"></emu-xref>, and returns the result of ILD transformation into _targetCase_ as a new String value.</dd>
+          <dd>It interprets _S_ as a sequence of UTF-16 encoded code points, as described in es2026, <emu-xref href="#sec-ecmascript-language-types-string-type"></emu-xref>, and returns the result of ILD transformation into _targetCase_ as a new String value.</dd>
         </dl>
         <emu-alg>
           1. Let _requestedLocales_ be ? CanonicalizeLocaleList(_locales_).
@@ -94,9 +94,9 @@ <h1>
     <emu-clause id="sup-string.prototype.tolocaleuppercase">
       <h1>String.prototype.toLocaleUpperCase ( [ _locales_ ] )</h1>
 
-      <p>This definition supersedes the definition provided in es2025, <emu-xref href="#sec-string.prototype.tolocaleuppercase"></emu-xref>.</p>
+      <p>This definition supersedes the definition provided in es2026, <emu-xref href="#sec-string.prototype.tolocaleuppercase"></emu-xref>.</p>
 
-      <p>This function interprets a String value as a sequence of code points, as described in es2025, <emu-xref href="#sec-ecmascript-language-types-string-type"></emu-xref>. The following steps are taken:</p>
+      <p>This function interprets a String value as a sequence of code points, as described in es2026, <emu-xref href="#sec-ecmascript-language-types-string-type"></emu-xref>. The following steps are taken:</p>
 
       <emu-alg>
         1. Let _O_ be ? RequireObjectCoercible(*this* value).
@@ -113,12 +113,12 @@ <h1>String.prototype.toLocaleUpperCase ( [ _locales_ ] )</h1>
   <emu-clause id="sup-properties-of-the-number-prototype-object">
     <h1>Properties of the Number Prototype Object</h1>
 
-    <p>The following definition(s) refer to the abstract operation thisNumberValue as defined in es2025, <emu-xref href="#sec-properties-of-the-number-prototype-object"></emu-xref>.</p>
+    <p>The following definition(s) refer to the abstract operation thisNumberValue as defined in es2026, <emu-xref href="#sec-properties-of-the-number-prototype-object"></emu-xref>.</p>
 
     <emu-clause id="sup-number.prototype.tolocalestring">
       <h1>Number.prototype.toLocaleString ( [ _locales_ [ , _options_ ] ] )</h1>
 
-      <p>This definition supersedes the definition provided in es2025, <emu-xref href="#sec-number.prototype.tolocalestring"></emu-xref>.</p>
+      <p>This definition supersedes the definition provided in es2026, <emu-xref href="#sec-number.prototype.tolocalestring"></emu-xref>.</p>
 
       <p>When the `toLocaleString` method is called with optional arguments _locales_ and _options_, the following steps are taken:</p>
 
@@ -133,12 +133,12 @@ <h1>Number.prototype.toLocaleString ( [ _locales_ [ , _options_ ] ] )</h1>
   <emu-clause id="sup-properties-of-the-bigint-prototype-object">
     <h1>Properties of the BigInt Prototype Object</h1>
 
-    <p>The following definition(s) refer to the abstract operation thisBigIntValue as defined in es2025, <emu-xref href="#sec-properties-of-the-bigint-prototype-object"></emu-xref>.</p>
+    <p>The following definition(s) refer to the abstract operation thisBigIntValue as defined in es2026, <emu-xref href="#sec-properties-of-the-bigint-prototype-object"></emu-xref>.</p>
 
     <emu-clause id="sup-bigint.prototype.tolocalestring">
       <h1>BigInt.prototype.toLocaleString ( [ _locales_ [ , _options_ ] ] )</h1>
 
-      <p>This definition supersedes the definition provided in es2025, <emu-xref href="#sec-bigint.prototype.tolocalestring"></emu-xref>.</p>
+      <p>This definition supersedes the definition provided in es2026, <emu-xref href="#sec-bigint.prototype.tolocalestring"></emu-xref>.</p>
 
       <p>When the `toLocaleString` method is called with optional arguments _locales_ and _options_, the following steps are taken:</p>
 
@@ -153,12 +153,12 @@ <h1>BigInt.prototype.toLocaleString ( [ _locales_ [ , _options_ ] ] )</h1>
   <emu-clause id="sup-properties-of-the-date-prototype-object">
     <h1>Properties of the Date Prototype Object</h1>
 
-    <p>The following definition(s) refer to the abstract operation thisTimeValue as defined in es2025, <emu-xref href="#sec-properties-of-the-date-prototype-object"></emu-xref>.</p>
+    <p>The following definition(s) refer to the abstract operation thisTimeValue as defined in es2026, <emu-xref href="#sec-properties-of-the-date-prototype-object"></emu-xref>.</p>
 
     <emu-clause id="sup-date.prototype.tolocalestring">
       <h1>Date.prototype.toLocaleString ( [ _locales_ [ , _options_ ] ] )</h1>
 
-      <p>This definition supersedes the definition provided in es2025, <emu-xref href="#sec-date.prototype.tolocalestring"></emu-xref>.</p>
+      <p>This definition supersedes the definition provided in es2026, <emu-xref href="#sec-date.prototype.tolocalestring"></emu-xref>.</p>
 
       <p>When the `toLocaleString` method is called with optional arguments _locales_ and _options_, the following steps are taken:</p>
 
@@ -175,7 +175,7 @@ <h1>Date.prototype.toLocaleString ( [ _locales_ [ , _options_ ] ] )</h1>
     <emu-clause id="sup-date.prototype.tolocaledatestring">
       <h1>Date.prototype.toLocaleDateString ( [ _locales_ [ , _options_ ] ] )</h1>
 
-      <p>This definition supersedes the definition provided in es2025, <emu-xref href="#sec-date.prototype.tolocaledatestring"></emu-xref>.</p>
+      <p>This definition supersedes the definition provided in es2026, <emu-xref href="#sec-date.prototype.tolocaledatestring"></emu-xref>.</p>
 
       <p>When the `toLocaleDateString` method is called with optional arguments _locales_ and _options_, the following steps are taken:</p>
 
@@ -192,7 +192,7 @@ <h1>Date.prototype.toLocaleDateString ( [ _locales_ [ , _options_ ] ] )</h1>
     <emu-clause id="sup-date.prototype.tolocaletimestring">
       <h1>Date.prototype.toLocaleTimeString ( [ _locales_ [ , _options_ ] ] )</h1>
 
-      <p>This definition supersedes the definition provided in es2025, <emu-xref href="#sec-date.prototype.tolocaletimestring"></emu-xref>.</p>
+      <p>This definition supersedes the definition provided in es2026, <emu-xref href="#sec-date.prototype.tolocaletimestring"></emu-xref>.</p>
 
       <p>When the `toLocaleTimeString` method is called with optional arguments _locales_ and _options_, the following steps are taken:</p>
 
@@ -213,7 +213,7 @@ <h1>Properties of the Array Prototype Object</h1>
     <emu-clause id="sup-array.prototype.tolocalestring">
       <h1>Array.prototype.toLocaleString ( [ _locales_ [ , _options_ ] ] )</h1>
 
-      <p>This definition supersedes the definition provided in es2025, <emu-xref href="#sec-array.prototype.tolocalestring"></emu-xref>.</p>
+      <p>This definition supersedes the definition provided in es2026, <emu-xref href="#sec-array.prototype.tolocalestring"></emu-xref>.</p>
 
       <p>When the `toLocaleString` method is called with optional arguments _locales_ and _options_, the following steps are taken:</p>
 
@@ -235,7 +235,7 @@ <h1>Array.prototype.toLocaleString ( [ _locales_ [ , _options_ ] ] )</h1>
       </emu-alg>
 
       <emu-note>
-        This algorithm's steps mirror the steps taken in es2025, <emu-xref href="#sec-array.prototype.tolocalestring"></emu-xref>, with the exception that Invoke(_nextElement_, *"toLocaleString"*) now takes _locales_ and _options_ as arguments.
+        This algorithm's steps mirror the steps taken in es2026, <emu-xref href="#sec-array.prototype.tolocalestring"></emu-xref>, with the exception that Invoke(_nextElement_, *"toLocaleString"*) now takes _locales_ and _options_ as arguments.
       </emu-note>
 
       <emu-note>