-
Notifications
You must be signed in to change notification settings - Fork 134
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
Date.toLocaleString slowdown since 3.52.2 #1057
Comments
@msvab Could you maybe create a repo with the contents of that zip? |
confirmed : code : https://github.com/romainmenke/intl-performance-issue-1 This code was run a 100 times in the reproduction for (var i = 0; i < 100; i++) {
var event = new Date(Date.UTC(2012, 11, 20, 3, 0, 0));
event.toLocaleString('es', { timeZone: 'UTC' });
} @longlho Can you take a look? |
hmm what about latest version? Those are super old versions that don't use |
@longlho The latest version 3.104.0 is actually the one where we discovered the slowdown. Then we went back to identify which was the last version with acceptable speed. |
https://github.com/Financial-Times/polyfill-library/compare/v3.53.2..v3.53.1
To me this is starting to look like polyfill list from 3.53.1
polyfill list from 3.53.2
|
What
We've noticed that Date.toLocaleString() has great performance degradation on IE11 since version 3.53.2. 3.53.1 is the most recent version which works fine.
Details
Attached is a very basic HTML page which shows the problem. Using version 3.53.1 the benchmark takes 157ms, but on 3.53.2 it takes 6400ms. We use this function to render dates on a datepicker and users with less powerful computers see the "page is not responding due to a long-running script" error.
test.zip
I'm happy to provide more details or if you can point me to the right direction to narrow this issue further?
The text was updated successfully, but these errors were encountered: