Engineers from Apple was present in the discussion of this spec change I will ask them tomorrow in TC39 TG2 meeting
On Wed, Nov 5, 2025 at 6:00 AM Chris Harrelson <[email protected]> wrote: > Hi, > > What about webkit? Could you file a standards position request for them? > > On Fri, Oct 31, 2025 at 6:07 PM Chromestatus < > [email protected]> wrote: > >> *Contact emails* >> [email protected] >> >> *Specification* >> https://tc39.es/ecma402/#sec-Intl.Locale.prototype.variants >> >> *Summary* >> Add Intl.Locale.prototype.variants as stated in >> https://tc39.es/ecma402/#sec-Intl.Locale.prototype.variants and also >> accept "variants" in option bag in Intl.Locale consturctor as in >> https://tc39.es/ecma402/#sec-updatelanguageid The changes to ECMA402 is >> merged in https://github.com/tc39/ecma402/pull/960 and the test code in >> test262 are merged in in https://github.com/tc39/test262/pull/4474/ >> >> *Blink component* >> Blink>JavaScript>Internationalization >> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EJavaScript%3EInternationalization%22> >> >> *Web Feature ID* >> intl-locale <https://webstatus.dev/features/intl-locale> >> >> *Motivation* >> TC39 already approve for the change so it is now part of ECMA402 spec. >> >> *Initial public proposal* >> *No information provided* >> >> *TAG review* >> *No information provided* >> >> *TAG review status* >> Issues addressed >> >> *Risks* >> >> >> *Interoperability and Compatibility* >> *No information provided* >> >> *Gecko*: Shipped/Shipping ( >> https://bugzilla.mozilla.org/show_bug.cgi?id=1970161) >> https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/141 >> >> *WebKit*: No signal >> >> *Web developers*: Strongly positive ( >> https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Locale/variants >> ) >> >> *Other signals*: >> >> *WebView application risks* >> >> Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> No >> >> >> *Debuggability* >> *No information provided* >> >> *Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, ChromeOS, Android, and Android WebView)?* >> Yes >> >> *Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* >> Yes >> Test262 https://github.com/tc39/test262/tree/main/test/intl402/Locale >> 'intl402/Locale/constructor-getter-order': >> 'intl402/Locale/constructor-options-throwing-getters': >> 'intl402/Locale/constructor-options-variants-invalid': >> 'intl402/Locale/constructor-options-variants-valid': >> 'intl402/Locale/getters-grandfathered': 'intl402/Locale/getters-missing': >> 'intl402/Locale/prototype/variants/name': >> 'intl402/Locale/prototype/variants/prop-desc': >> >> *Flag name on about://flags* >> *No information provided* >> >> *Finch feature name* >> *No information provided* >> >> *Non-finch justification* >> *No information provided* >> >> *Rollout plan* >> Will ship enabled for all users >> >> *Requires code in //chrome?* >> False >> >> *Availability expectation* >> Feature is available on Web Platform Baseline within 12 months of launch >> in Chrome. >> >> *Adoption expectation* >> Feature is considered a best practice for some use case within 12 months >> of reaching Web Platform baseline. >> >> *Non-OSS dependencies* >> >> Does the feature depend on any code or APIs outside the Chromium open >> source repository and its open-source dependencies to function? >> NO >> >> *Estimated milestones* >> Shipping on desktop 144 >> Shipping on Android 144 >> Shipping on WebView 144 >> >> *Anticipated spec changes* >> >> Open questions about a feature may be a source of future web compat or >> interop issues. Please list open issues (e.g. links to known github issues >> in the project for the feature specification) whose resolution may >> introduce web compat/interop risk (e.g., changing to naming or structure of >> the API in a non-backward-compatible way). >> *No information provided* >> >> *Link to entry on the Chrome Platform Status* >> https://chromestatus.com/feature/4709921706868736?gate=5072143612248064 >> >> *Links to previous Intent discussions* >> Intent to Prototype: >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68e5bd35.050a0220.3258b8.05f2.GAE%40google.com >> Ready for Trial: >> https://groups.google.com/a/chromium.org/g/blink-dev/c/i6QEHcH_fiI/m/4xUyZbSvAAAJ >> >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com>. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69053325.710a0220.23debc.0105.GAE%40google.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69053325.710a0220.23debc.0105.GAE%40google.com?utm_medium=email&utm_source=footer> >> . >> > -- Frank Yung-Fong Tang 譚永鋒 / 🌭🍊 Sr. Software Engineer -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2B7fzPGcNd03P0zf0h_biWcdWEmX3AwNPCntkGZ3mj%3DycMxibw%40mail.gmail.com.
