FS#76773 - [chromium] fails to parse date strings, causes infinite loop
Attached to Project:
Arch Linux
Opened by Leon Sorokin (leeoniya) - Wednesday, 07 December 2022, 23:05 GMT
Last edited by Evangelos Foutras (foutrelis) - Thursday, 08 December 2022, 01:24 GMT
Opened by Leon Sorokin (leeoniya) - Wednesday, 07 December 2022, 23:05 GMT
Last edited by Evangelos Foutras (foutrelis) - Thursday, 08 December 2022, 01:24 GMT
|
Details
Description:
Chromium fails to parse date strings produced by Date.toLocaleString()...but Chrome and Firefox work as expected. This appears to be isolated to Arch/Chromium or EndeavourOS/Chromium. I've tested this on Chromium in Windows 10 as well as Chromium on PoP_OS (a Ubuntu derivative), and everything works consistently between Chromium and Chrome on those platforms. Additional info: OS: EndeavourOS (fully updated 2022-12-06) DE: KDE/Plasma Package: extra/chromium 108.0.5359.94-2 Steps to reproduce: you can visit this URL in Chromium and watch the tab crash. opening the same link in Chrome or Firefox works as expected: https://leeoniya.github.io/uPlot/demos/timezones-dst.html Additional context: https://github.com/grafana/grafana/issues/58728#issuecomment-1333135075 the problem has been isolated to a difference in Date parsing behavior. paste the following into Chromium, Chrome, and Firefox DevTools console: let date = new Date(1667594981087); let date2 = new Date(date.toLocaleString('en-US', {timeZone: 'America/New_York'})); console.log(date); console.log(date2); // Invalid Date ?? |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Thursday, 08 December 2022, 01:24 GMT
Reason for closing: Fixed
Additional comments about closing: chromium 108.0.5359.98-2
Thursday, 08 December 2022, 01:24 GMT
Reason for closing: Fixed
Additional comments about closing: chromium 108.0.5359.98-2
FS#76655is related... Edit: yep, see below.for (var dt = new Date("3/01/" + yr + " 00:00:00"), found = 0; found < 2; )
Thanks for the detailed report (and good catch Toolybird about
FS#76655).