js-128.3.1 (spidermonkey)

[Xi Ruoyao]

New ESR release.

[Xi Ruoyao]

gjs MR: ​https://gitlab.gnome.org/GNOME/gjs/-/merge_requests/936

[Xi Ruoyao]

Removed GNOME 47 in subject because the milestone is enough to show it.

[Xi Ruoyao]

Per Firefox release note there are security fixes in js component.

[Xi Ruoyao]

Reassign to myself. Already discussed with Douglas via IRC.

[Xi Ruoyao]

125:

• Intl.Segmenter is now supported, allowing developers to perform locale-sensitive text segmentation of a string. This enables, for example, splitting a string into words in languages that don't use spaces to separate them: Intl.Segmenter("ja-JP", { granularity: "word" }). You can also split strings into graphemes or sentences. (Firefox bug 1423593, Firefox bug 1883914.)

124:

• No notable changes.

123:

JavaScript

• The Date.parse() global object has had a number of bug fixes to bring it into line with how other browsers parse the values being passed.
  • Incorrect day of month (e.g. "31 April") now skips over to the following month (e.g. "1 May"). (Firefox bug 1872333).
  • Incomplete time zone (e.g. "1/1/70 gm") or AM/PM (e.g. "1/1/70 10:00 a") are no longer accepted. (Firefox bug 1870570).
  • Single number dates are now accepted (e.g. Date.parse("0") now returns 946684800000 - Sat Jan 01 2000 00:00:00). (Firefox bug 1870434).

122:

• The ArrayBuffer.prototype.transfer() and ArrayBuffer.prototype.transferToFixedLength() methods can now be used to transfer ownership of memory from one ArrayBuffer to another. After transfer, the original buffer is detached from its original memory and hence unusable; the state can be checked using ArrayBuffer.prototype.detached. (See Firefox bug 1865103 for more details.)
• For parity with other browsers, Date.parse() and the Date() constructor only consider the first three letters of the specified month when non-standard date strings are parsed. Previously only truncated values of the full month name with three or more characters were accepted (See Firefox bug 1862910 for more details.)

121:

• The Promise.withResolvers() static method is now supported. This exposes the resolve and reject callback functions in the same scope as the returned Promise, allowing code that resolves or rejects the promise to be defined after its construction (Firefox bug 1845586).
• Date.parse() now accepts several additional date formats:
  • Year > 9999 for YYYY-MMM-DD format (e.g. 19999-Jan-01) (Firefox bug 1858851)
  • MMM-DD-YYYY (e.g. Jan-01-1970) (Firefox bug 1863489)
  • Milliseconds for non-ISO date formats (e.g. Jan 1 1970 10:00:00.050) (Firefox bug 1863125)
  • Day of week at the beginning of formats which were being rejected, such as:
    • Wed, 1970-01-01
    • Wed, 1970-Jan-01
    The day of week does not need to be correct, or a day of week at all; for example, foo 1970-01-01 works (Firefox bug 1617562).
• Other Date.parse() fixes:
  • YYYY-M-DD and YYYY-MM-D are no longer assumed GMT as an ISO date YYYY-MM-DD would be (Firefox bug 1783731).
  • Milliseconds for all formats are truncated after 3 digits, rather than being rounded (Firefox bug 746529).

120:

• Date.parse() now accepts several additional date formats:
  • Numeric dashed dates which do not meet the formal ISO standard are now accepted (Firefox bug 1557650), including:
    • "01-12-1999" (month first)
    • "1999-1-5" (single-digit month or day)
    • "10000-01-12" (year > 9999)
    • "99-01-05" or "01-05-99" (2-digit year, year must be >31 if it comes first)
    • "1999-01-05 10:00:00" (space between date and time).
    These dates will be parsed with behavior typical of other non-ISO dates, such as local time zone and month rollover (April 31 rolls over to May 1 since April 31 doesn't exist).
  • Requirements for characters directly following numbers have been loosened to accept new formats (Firefox bug 449921), including:
    • "DDMonYYYY"
    • "Mon.DD.YYYY"
    • "DD.Mon.YYYY"
    • "YYYY.MM.DD"
    • "Mon DD YYYY hh:mmXm" (am/pm directly following time)
  • Timezone 'Z' is now accepted for non-ISO formats (e.g. Jan 1 1970 10:00Z) (Firefox bug 1852422)

119:

• The Object.groupBy() and Map.groupBy() static methods for grouping the elements of an iterable are now supported (See Firefox bug 1792650 for more details.)
• The String.prototype.isWellFormed() and String.prototype.toWellFormed() methods respectively can be used to check if a string contains well-formed Unicode text (i.e. contains no lone surrogates) and sanitize an ill-formed string to well-formed Unicode text. (See Firefox bug 1850755 for more details).

118:

• No notable changes.

117:

• No notable changes.

116:

• Intl.NumberFormat supports new constructor options that control how numbers are rounded (roundingIncrement, roundingMode, roundingPriority), the strategy for displaying trailing zeros on whole numbers (trailingZeroDisplay), and whether to use grouping separators to indicate thousands, millions, and so on (useGrouping). It also supports new methods formatRange() amd formatRangeToParts() for formatting ranges of numbers. (Firefox bug 1795756).
• Intl.PluralRules was updated (as part of the same set of changes as Intl.NumberFormat) to support constructor options roundingIncrement, roundingMode, roundingPriority and trailingZeroDisplay, and the selectRange() method. (Firefox bug 1795756).

[Xi Ruoyao]

Fixed r12.2-356-g4e23a06110, left open for a SA.

[Douglas R. Reno]

SA-12.2-027 issued