Ready for Developer Testing: Intl.DurationFormat

[Frank Tang]

Contact emails

ft...@google.com

Explainer

https://github.com/tc39/proposal-intl-duration-format

Specification

https://tc39.es/proposal-intl-duration-format

Design docs

https://docs.google.com/document/d/1UMwkeeiqVyVNhNW8CS1vwN9g2cIH0AryaU16DT-vGg0/edit

Summary

Intl.DurationFormat API is a TC39 ECMA402 proposal See https://github.com/tc39/proposal-intl-duration-format for the proposal The proposal advanced to Stage 3 on 2021-10 Spec: https://tc39.es/proposal-intl-duration-format/

Blink component

Blink>JavaScript>Internationalization

TAG review

None

TAG review status

Not applicable

Risks

Interoperability and Compatibility

The spec is sync with Temporal . If Temporal dramatically change the definition of Temporal Duration, we may need to adjust the implemetation

Gecko: Positive (https://bugzilla.mozilla.org/show_bug.cgi?id=1648139)

WebKit: Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=214794) https://developer.apple.com/documentation/safari-release-notes/safari-16_4-release-notes

Web developers: Positive (https://github.com/tc39/ecma402-mdn/issues/22) https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DurationFormat

Other signals:

Ergonomics

Temporal.Duration as defined in https://tc39.es/proposal-temporal/#sec-temporal-maximumtemporaldurationroundingincrement

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?

low

Goals for experimentation

Ongoing technical constraints

None

Debuggability

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?

Yes

https://github.com/tc39/test262/issues/3305

Flag name on chrome://flags

harmony_intl_duration_format

Finch feature name

None

Non-finch justification

v8

Requires code in //chrome?

False

Tracking bug

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

Measurement

Use Count CL is under review in https://chromium-review.googlesource.com/c/chromium/src/+/5646725

Availability expectation

Feature is available on Web Platform mainline within 6 months of launch in Chrome.

Adoption expectation

Feature is considered a best practice for some use case within 6 months of reaching Web Platform baseline.

Adoption plan

intl dev team inside google will rewrite closure duration format to use this feature with a thinner wrapper

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?

The feature depend on ICU and therefore also CLDR project

Estimated milestones

DevTrial on desktop

128

DevTrial on Android

128

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).

https://github.com/tc39/proposal-intl-duration-format/issues

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5193021205774336

Links to previous Intent discussions

Intent to prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOcELL-vykLL8UDTG1QcKptGfyRPw8T6StP2%2BqMPFv09aUHPbg%40mail.gmail.com

This intent message was generated by Chrome Platform Status.