Chrome v67 timezones are broken! Why? | Sololearn: Learn to code for FREE!
Новый курс! Каждый программист должен знать генеративный ИИ!
Попробуйте бесплатный урок
+ 82

Chrome v67 timezones are broken! Why?

After Chrome version 67.0.3366.0 the old date timezones are broken. You can try it with: new Date(Date.parse("1/5/1880 GMT")).toString(); You can try it on other browsers and see the correct results. For example, if you are in Central Europe, for 2018 it will display GMT+0100 (which is correct) but for 1880 GMT+0053 (which is wrong). In case of Dubai it will become GMT+0400 and GMT+0341 in the same order. Please explain it in details and not only put some links in the comments.

14th Jun 2018, 12:52 PM
Aaron Sarkissian
Aaron Sarkissian - avatar
31 ответ
+ 55
I speculate that it has something to do with Standard Time not having been adopted worldwide in 1880. According to Wikipedia it had been proposed by then, but acceptance came slowly over the next 50 years or so. Google might be computing Solar Local Time that far back. Just throwing the idea out there - I haven't checked the numbers.
15th Jun 2018, 3:15 AM
Brian - avatar
+ 15
it's not broken it's a feature of Chrome
16th Jun 2018, 4:41 PM
James Hill
James Hill - avatar
+ 13
Hi Aaron Sarkissian I saw this on stackoverflow and interesting. Maybe you saw it too.
17th Jun 2018, 6:46 PM
cyber33 - avatar
+ 9
it seems that after chrome 67 timezone is some how rounding of the time like in India it shows GMT+0521 old time and new time it shows GMT+0530 so the new update somehow taking the IANA timezone rather than os time zone or it just rounding of the time to its Ceil value Aaron Sarkissian thanks for sharing this I don't know correctly about that sorry but want to know about that so bookmarking
14th Jun 2018, 1:31 PM
MsJ - avatar
+ 8
Jan Markus c'mon dude! I bet you don't use dates older than 1970 on daily basis 😃
14th Jun 2018, 3:06 PM
Aaron Sarkissian
Aaron Sarkissian - avatar
+ 7
i think u need to go ask Sundar Pichai!
16th Jun 2018, 5:15 PM
Siddharth - avatar
+ 7
May be a bug which need to be fixed
17th Jun 2018, 7:13 AM
A N S H U L   S I N G H - avatar
+ 7
geez you people need to stop down voting so many posts.....
18th Jun 2018, 1:51 PM
Ole113 - avatar
+ 5
is a feature until they update it for something else.
16th Jun 2018, 5:57 PM
James Hill
James Hill - avatar
+ 5
Monique Boodram ohk,I mean ok am an environmentalist but I think dinosaurs won't like me that much that. Jan Markus making others fight!!! that's too human like thing😂😂
16th Jun 2018, 7:15 PM
LELOUCH - avatar
+ 4
why am i this confuse here 😭😭
16th Jun 2018, 7:32 PM
Kingsley Ebong
Kingsley Ebong - avatar
+ 4
so much confusion 😢
16th Jun 2018, 9:49 PM
Esther Omoathebu
Esther Omoathebu - avatar
+ 3
Jan Markus I don't think it is possible to travel back in time, even if you do travel into past the world line has to change even if you make no difference in the events, because the reality is that you didn't go there....
14th Jun 2018, 3:42 PM
LELOUCH - avatar
+ 2
is it incorrectly adjusting for leap days, leap minutes or leap seconds? 2000 was not a leap year because every 400 years we have to skip 1 since the every 4 year pattern over compensates for the imprecision in a 365 day year compared to the actual hours, minutes , and seconds required to orbit the sun.
17th Jun 2018, 1:07 AM
SQrL - avatar
+ 2
I am not understand about that how can do it 😕
17th Jun 2018, 2:58 PM
Shreya Jain
Shreya Jain - avatar
+ 2
Thats a feature of google chrome
18th Jun 2018, 2:30 PM
+ 1
Ya'll need to exploit every little detail to hack google. and win the one billion challenge l 😅.. anybody in!? .. ps : just kidding.
17th Jun 2018, 8:16 AM
Ajjuniors - avatar
+ 1
it's a future of chrome
17th Jun 2018, 8:37 AM
Archana Berad
+ 1
It is not broken
17th Jun 2018, 8:58 AM
Ferdinand Israel
Ferdinand Israel - avatar
+ 1
why does chrome support it knowing its broken? any idea?
18th Jun 2018, 11:30 AM
Petest Sam
Petest Sam - avatar