[ http://issues.apache.org/jira/browse/WICKET-103?page=all ]
Eelco Hillenius resolved WICKET-103.
------------------------------------
Fix Version/s: 1.3
2.0
Resolution: Fixed
> BrowserInfoPage yields incorrect offset
> ---------------------------------------
>
> Key: WICKET-103
> URL: http://issues.apache.org/jira/browse/WICKET-103
> Project: Wicket
> Issue Type: Bug
> Reporter: Eelco Hillenius
> Fix For: 1.3, 2.0
>
>
> 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)'.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
