You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 14, 2021. It is now read-only.
Executing new Intl.DateTimeFormat('en-US').formatToParts(new Date())); in a browser that has native Intl API implementation (Chrome, FFox, ...) results in:
TypeError: (intermediate value).formatToParts is not a function
Would it make sense for this polyffill to monkey-patch the Intl object so new methods like formatToParts can be used in browsers already having Intl API partly implemented? Or is this considered gross?
Is using IntlPolyfill a preferred way to go then?
The text was updated successfully, but these errors were encountered:
Executing
new Intl.DateTimeFormat('en-US').formatToParts(new Date()));
in a browser that has nativeIntl
API implementation (Chrome, FFox, ...) results in:Would it make sense for this polyffill to monkey-patch the Intl object so new methods like
formatToParts
can be used in browsers already havingIntl
API partly implemented? Or is this considered gross?Is using
IntlPolyfill
a preferred way to go then?The text was updated successfully, but these errors were encountered: