-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
timezone plugin broken in IE11 (unsupported method) #1489
Comments
+1 |
I also ran into this issue. I tried the recommended polyfill from your docs, but this polyfill does not support |
I now found a way to make this work. There were 2 things that I had to change:
It obviously feels a little hacky, but solves the problem. So I think it would be good if the documentation was updated and going a little more into detail how timezones can be made to work in IE 11. |
+1 |
These expressions have different meanings and produce different results, they should not be used interchangeably.
This comment formatjs/formatjs#2529 (comment) explains how to polyfill import '@formatjs/intl-getcanonicallocales/polyfill';
import '@formatjs/intl-locale/polyfill';
import '@formatjs/intl-pluralrules/polyfill'
import '@formatjs/intl-pluralrules/locale-data/en' // locale-data for en
import '@formatjs/intl-numberformat/polyfill'
import '@formatjs/intl-numberformat/locale-data/en' // locale-data for en
import '@formatjs/intl-datetimeformat/polyfill'
import '@formatjs/intl-datetimeformat/locale-data/en' // locale-data for en
import '@formatjs/intl-datetimeformat/add-all-tz' // Add ALL tz data |
Describe the bug
Intl.DateTimeFormat.formatToParts
is not supported in IE11. This method is used by the timezone plugin here. Using the plugin in IE11 results in a runtime error.Expected behavior
IE11 support. Documentation states "Currently the following browsers are used for the ci system: Chrome on Windows XP, IE 8, 9, and 10 on Windows 7, IE 11 on Windows 10, latest Firefox on Linux, and latest Safari on OSX 10.8 and 10.11."
Information
The text was updated successfully, but these errors were encountered: