[Webkit-unassigned] [Bug 209778] New: Intl.DateTimeFormat.prototype.formatRange missing in WebKit
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Mar 30 14:50:13 PDT 2020
https://bugs.webkit.org/show_bug.cgi?id=209778
Bug ID: 209778
Summary: Intl.DateTimeFormat.prototype.formatRange missing in
WebKit
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: JavaScriptCore
Assignee: webkit-unassigned at lists.webkit.org
Reporter: sffc at chromium.org
The formatRange function for Intl.DateTimeFormat is at Stage 3 in TC39; the proposal is on track to reach Stage 4 in 2020. V8 has had it ready for some time, and SpiderMonkey plans to add it in the first half of this year.
As usage of formatRange in Intl.DateTimeFormat increases throughout the ecosystem, WebKit users will be left behind with legacy polyfills, leading to broken web sites and/or poorer performance relative to other browsers. At Google, we are currently weighing our options for calling these features of formatRange in Intl.DateTimeFormat in supported environments in order to give users better performance and smaller download sizes.
ICU4C exposes C and C++ APIs that can be used to implement formatRange in Intl.DateTimeFormat. Implementing formatRange in Intl.DateTimeFormat is largely a matter of adding the glue between JavaScript and ICU4C, as WebKit already does for other Intl types.
Proposal repo: https://github.com/fabalbon/proposal-intl-DateTimeFormat-formatRange
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200330/4c438ba5/attachment.htm>
More information about the webkit-unassigned
mailing list