New issue
Advanced search Search tips

Issue 830918 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 818249
Owner: ----
Closed: Apr 2018
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

getTimezoneOffset() returns 0 after changing timezone until Chrome is restarted

Project Member Reported by aanheuser@google.com, Apr 9 2018

Issue description

Chrome Version       : 65.0.3325.181
OS Version: OS X 10.13.3
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari: OK
    Firefox: FAIL
    IE/Edge: don't know

What steps will reproduce the problem?
1. Run `new Date().getTimezoneOffset()` in console, note offset
2. Change timezone to some other one
3. Re-run `new Date().getTimezoneOffset()`. Note how it returns 0 until you restart Chrome, no matter what timezone you set.

What is the expected result?
It returns the new timezone offset.

What happens instead of that?
It returns 0 independent of timezone until Chrome is restarted.

UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36



 
Labels: Needs-Triage-M65

Comment 2 by rsesek@chromium.org, Apr 10 2018

Mergedinto: 818249
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment