getTimezoneOffset() returns incorrect value after changing system timezone
Reported by
swi...@gmail.com,
Feb 23 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36 Steps to reproduce the problem: 1. Run `new Date().getTimezoneOffset()` // correct value 2. Change your system time zone 3. Run `new Date().getTimezoneOffset()` // returns 0 4. Restart chrome 5. Run `new Date().getTimezoneOffset()` // returns correct value again What is the expected behavior? I expect getTimezoneOffset() to always return the correct offset from UTC for the user's computer. What went wrong? If a user changes their timezone without restarting Chrome, the getTimezoneOffset() starts returning 0 no matter what the timezone is changed to. Even if you change it back to the original value, JavaScript still thinks offset is 0. Did this work before? N/A Chrome version: 64.0.3282.167 Channel: n/a OS Version: OS X 10.13.2 Flash Version:
,
Feb 25 2018
,
Feb 25 2018
,
Feb 27 2018
Unable to reproduce the issue on mac 10.13.3 using chrome reported version #64.0.3282.167 and latest canary #66.0.3355.0. Attached a screen cast for reference. Following are the steps followed to reproduce the issue. ------------ 1. Ran `new Date().getTimezoneOffset()` 2. Got correct value. 3. Changed system time zone 4. Again ran `new Date().getTimezoneOffset()` 5. Got correct value without restarting. swizec@ - Could you please check the issue on latest canary #66.0.3355.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Thanks...!!
,
Apr 2 2018
Mac triage: WontFix old issue without feedback or repro. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by swi...@gmail.com
, Feb 23 2018