Issues

Issue #57 wontfix

Wrong time zone using Chrome on Mac

javiervegas
created an issue

OSX 10.8.2 (Mountain Lion) Chrome 24.0.1312.57 (latest version available)

When my date & time preferences are set to "America/Los Angeles" (my real time zone) the demo http://pellepim.bitbucket.org/jstz/ detects it correctly. When my date & time preferences are set to anything else (for example "America/New_York", "Australia/Adelaide", "Europe/London", "Asia/Tokio", etc), the script always returns "Pacific/Pitcairn"

Comments (4)

  1. javiervegas reporter

    Update: Setting back my date & time settings to America/Los_Angeles, the demo on Chrome still says "Pacific/Pitcairn". Safari and Firefox had always the correct timezones for all the tests.

  2. javiervegas reporter

    Ok, I just read issue #52 and I am hitting the same Chrome problem. After a bit more testing, this is what I am seeing: 1) Changing my time zone settings and opening a new Chrome tab/window, the demo script shows me the good timezone 2) Changing again the timezone setting and reloading the demo, it shows me a wrong timezone (usually Pacific/Pitcairn but I have also seen Africa/Lagos and America/Bogota, and keeps showing that if I keep changing the timezone 3) Opening a new new Chrome tab/window, the demo script shows me the correct timezone

  3. Jon Nylander repo owner

    This is not a bug in jsTimezoneDetect, Chrome does not pick up on time zone changes until a new tab is opened or the browser restarted. Hence "wont fix"

    Thanks for reporting though.

  4. Log in to comment