[WICKET-103] BrowserInfoPage yields incorrect offset

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0 branch (discontinued), 1.3.0-beta1
• Assignee: Unassigned
• Reporter: Eelco Hillenius
• Created: 23/Nov/06 02:04
• Updated: 23/Nov/06 02:07
• Resolved: 23/Nov/06 02:06

Description

The BrowserInfoPage and ClientProperties currently give the wrong result for the timezone. It's hard to decide on what to fix, but I'm settling for fixing the javascript side. JavaScript's 'Date().getTimezoneOffset()' gives the time to be substracted from UTC and is thus the opposite of what you would (or at least I would) expect from that function. For instance, the offset for Seattle currently gets +8, while the time zone is -8. So... in order to let ClientProperties stay the same in case clients depend on it's behavior, I'll make the fix in BrowserInfoPage, changing from '(new Date().getTimezoneOffset() / 60)' to '(new Date().getTimezoneOffset() / -60)'.