Ready for Trial: Extend Intl.DateTimeFormat timeZoneName Option

21 views
Skip to first unread message

Frank Tang

unread,
May 27, 2021, 10:37:32 PMMay 27
to blink-dev, Mathias Bynens, Shane Carr, Nebojša Ćirić, Shu-yu Guo, Jakob Kummerow

Contact emails

ft...@google.com

Specification

https://tc39.es/proposal-intl-extend-timezonename/

Summary

Add 4 new values "shortGeneric", "longGeneric", "shortOffset", and "longOffset" for Intl.DateTimeFormat timeZoneName option



Blink component

Blink>JavaScript>Internationalization

TAG review

None

TAG review status

Not applicable

Risks



Interoperability and Compatibility



Gecko: In development (https://bugzilla.mozilla.org/show_bug.cgi?id=1710429)

WebKit: No signal

Web developers: No signals

Ergonomics

This is adding four new values to pre-existing API and pre-existing option property. So should be very easy to use with no additional ergonomic risk.



Activation

This is adding four new values to pre-existing API and pre-existing option property. So should be very easy to use with no additional activation risk.



Security

This is adding four new values to pre-existing API and pre-existing option property. So should be very easy to use with no additional security risk.



Goals for experimentation

None



Ongoing technical constraints

None



Debuggability

This is adding four new values to pre-existing API and pre-existing option property. So should carry the same amount of debuggability.



Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

No

Is this feature fully tested by web-platform-tests?

Yes

Flag name

harmony_intl_more_timezone

Tracking bug

https://bugs.chromium.org/p/v8/issues/detail?id=11661

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/4506375298220032

This intent message was generated by Chrome Platform Status.
Reply all
Reply to author
Forward
0 new messages