Intl Locale Info API is a Stage 3 ECMAScript TC39 proposal to enhance the Intl.Locale object by exposing Locale information, such as week data (first day in a week, weekend start day, weekend end day, minimun day in the first week), and text direction hour cycle used in the locale. https://github.com/tc39/proposal-intl-locale-info We ship our implementation in m99 (https://chromestatus.com/feature/5566859262820352 ) . But later on the propose made some change in Stage 3 and move several getters to functions. We need to remove the deprecated getters and relaunch the renamed functions
no other browser currently shipped with the removed getters. The earlier version of Safari has shipped it but removed a while ago (see below)
low. remove getters
low. Since Mozilla never have these getters and Safari had it in version 15 but also removed them in version 17 already.
none
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
https://github.com/tc39/test262/tree/main/test/intl402/Locale
Shipping on desktop | 133 |
Origin trial desktop first | 131 |
Origin trial desktop last | 133 |
DevTrial on desktop | 131 |
Shipping on Android | 133 |
Origin trial Android first | 131 |
Origin trial Android last | 133 |
DevTrial on Android | 131 |
Origin trial WebView first | 131 |
Origin trial WebView last | 133 |
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).
NoneIs this request to just deprecate them or is it to remove them as well, right away or at a future set date?
Secondly, you say usage is low, which makes a lot of sense, but
do we know how low? Are there Use Counters or some other hard
number we can lean on?
/Daniel
--
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 blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6733bbcd.2b0a0220.26ec07.0802.GAE%40google.com.
Is this request to just deprecate them or is it to remove them as well, right away or at a future set date?
Secondly, you say usage is low, which makes a lot of sense, but do we know how low? Are there Use Counters or some other hard number we can lean on?
Thanks Frank.
4% as an upper bound is a very, very large number, so I think we
should wait until we have proper UseCounter data for each of the
getters to better understand the compatibility risk.