Closed Bug 1710429 Opened 2 years ago Closed 2 years ago

Implement Extended TimeZoneName Options for Intl.DateTimeFormat

Categories

(Core :: JavaScript: Internationalization API, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
91 Branch
Tracking Status
firefox91 --- fixed

People

(Reporter: yulia, Assigned: anba)

References

(Blocks 1 open bug, )

Details

(Keywords: dev-doc-complete)

Attachments

(1 file)

Implement the proposal from https://github.com/tc39/proposal-intl-extend-timezonename.

Also includes some basic tests to cover the four new options.

Assignee: nobody → andrebargull
Status: NEW → ASSIGNED
Pushed by andre.bargull@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/1dc0676764f0
Implement "Extended TimeZoneName Options for Intl.DateTimeFormat" proposal. r=yulia
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch

Hi, I'm documenting this for FF91. The docs part is here: https://github.com/mdn/content/pull/6853. I still need to add browser compatibility information (all docs work can be tracked in https://github.com/mdn/content/issues/6710)

A question, in the proposal it refers to "localised" and "generic non-local forms". I know what localised means, but what does "non-local" mean?

That term stems from https://unicode.org/reports/tr35/tr35-dates.html#dfst-zone, which has definitions for:

  • specific non-location format
  • generic non-location format
  • generic location format.

So "non-location" simply refers to not using the name of the time zone identifier's location. For example "Pacific Time" for the time zone "America/Los_Angeles" instead of using "Los Angeles Time".

Thank you. That was my assumption but I was confused because if you do timezone America/Los_Angeles for German then the shortGeneric is Los Angeles Zeit on FF91. That link is helpful because it shows that there are fallbacks that are location based. Thanks!

FYI FF91 docs work is still waiting on browser compatibility update to complete but is otherwise good. If interested see docs PR and this release note PR.

You need to log in before you can comment on or make changes to this bug.