Closed Bug 377366 Opened 19 years ago Closed 9 years ago

GetTimezoneoffset returns wrong value when the system is kept to mid-atlantic timezone

Categories

(Core :: JavaScript Engine, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED WONTFIX

People

(Reporter: writekdp, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.11) Gecko/20070312 Firefox/1.5.0.11 Build Identifier: 1.5.0.11 when I changed the timezone of my XP system to mid-atlantic, the timezoneoffset value is being returned as 60... however it should be 120. (new Date()).getTimezoneOffset() when the system timezone is set to mid-atlantic Mid-atlantic timezoneoffset will always should be 120 not depending on DST. No DST applicable. Reproducible: Always Steps to Reproduce: Change the system timezone to mid-atlantic and have this (new Date()).getTimezoneOffset() in a script and run. It will return 60 instead of 120. Actual Results: value is 60 Expected Results: value should be 120
This sounds like a duplicate of bug 285615. Durga, can you confirm? Does restarting the browser after changing time zones fix the problem?
Its not a duplicate as after the restart of the firefox too, it is happening. I feel it is happening only for that mid-atlantic timezone and is too specific.
Assignee: general → nobody
Microsoft deprecated the Mid-Atlantic time zone in https://support.microsoft.com/en-us/kb/2904266, and in current Windows versions (tested Win7 and Win10) it's no longer possible to select this time zone. Therefore resolving as Won't fix.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.