Chrome does not pick up on time zone changes until the browser is restarted. (via: pellepim / jsTimezoneDetect / issues / #57 – Wrong time zone using Chrome on Mac — Bitbucket)
Posted by jpluimers on 2014/02/11
Just got bitten by Wrong time zone using Chrome on Mac:
Chrome does not pick up on time zone changes until a new tab is opened or the browser restarted.
Actually, it requires a browser restart, as below is the difference between a new Chrome tab and running on jsc on the console: https://gist.github.com/jpluimers/8933710
I’m in Amsterdam, my Mac is set to UTC+1 as TimeZone.
Chrome gets it wrong: it still thinks I’m in Florida (I was when I suspended the Mac, but then the Mac adjusted when coming out of sleep after the flight to Amsterdam).
Only after restarting Chrome, it got it right.
The code shows both the time zone based (new Date()) as the UTC based (toUTCString()) time stamps.
Note I didn’t bother to install jsTimezoneDetect that would have gotten readable time zone names, but I’m glad he answered the question.
Readable time zone names can get you confused though, as this is what BitBucket’s JIRA indicated:
Your computer’s time zone does not appear to match your user setting of (GMT-05:00) Bogota. Click here to update your settings. Alternatively, hide this message.
–jeroen
via: pellepim / jsTimezoneDetect / issues / #57 – Wrong time zone using Chrome on Mac — Bitbucket.
Leave a Reply