Does this feature change the behavior of existing web-exposed APIs for Locale? If so, what is the compat risk of breaking existing sites?
On Thu, Aug 22, 2024 at 4:11 PM Chromestatus < ad...@cr-status.appspotmail.com> wrote: > Contact emails ft...@google.com > > Explainer None > > Specification https://tc39.es/proposal-intl-locale-info > > Design docs > > https://docs.google.com/document/d/1BSpa-LKE69LL1g5CHZ3G06XEfffauwS24atfSUQiIDY/edit?usp=sharing > > Summary > > Intl Locale Info API is a new Stage 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 launch Intl Locale > Info API w/ getters but later the proposal changed to rename these getters > to functions. We need to deprecate the getter and relaunch the functions . > The deprecation of getters is tracked in > https://chromestatus.com/feature/5148228059398144 > > > Blink component Blink>JavaScript>Internationalization > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EJavaScript%3EInternationalization> > > TAG review None > > TAG review status Not applicable > > Risks > > > Interoperability and Compatibility > > None > > > *Gecko*: Positive (https://bugzilla.mozilla.org/show_bug.cgi?id=1693576) > > *WebKit*: Shipped/Shipping ( > https://developer.apple.com/documentation/safari-release-notes/safari-17-release-notes) > Shipped in Safari version 17 > > *Web developers*: Positive ( > https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Locale/getCalendars) > > https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Locale/getCalendars > https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Locale/getCollations > https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Locale/getHourCycles > https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Locale/getNumberingSystems > https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Locale/getTextInfo > https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Locale/getTimeZones > https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Locale/getWeekInfo > > *Other signals*: > > Ergonomics > > minor change, similar to all other functions in Intl.Locale object already. > > > Activation > > non- minor change, similar to all other functions in Intl.Locale object > already. > > > Security > > none - minor change, similar to all other functions in Intl.Locale object > already. > > > 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? > > None > > > Debuggability > > minor change, similar to all other functions in Intl.Locale object already. > > > 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 > > > https://github.com/tc39/test262/tree/main/test/intl402/Locale/prototype/get* > > > Flag name on chrome://flags None > > Finch feature name None > > Non-finch justification None > > Requires code in //chrome? False > > Tracking bug https://issues.chromium.org/issues/42203769 > > Sample links > > https://github.com/tc39/proposal-intl-locale-info?tab=readme-ov-file#high-level-design > > Estimated milestones > Shipping on desktop 130 > DevTrial on desktop 129 > Shipping on Android 130 > DevTrial on Android 129 > > 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). > None > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5122839207477248?gate=5125593355255808 > > Links to previous Intent discussions Ready for Trial: > https://groups.google.com/a/chromium.org/g/blink-dev/c/fIZhzp4AWbk/m/bocUBCXbBwAJ > > > 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 blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/000000000000f3725c06204dc61d%40google.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/000000000000f3725c06204dc61d%40google.com?utm_medium=email&utm_source=footer> > . > -- 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+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9DmZbTrY_W6wfe_xipQ_LO%2Bq6rR%3DBv__E7z544DAEW1g%40mail.gmail.com.
