You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Timo Rantalaiho (JIRA)" <ji...@apache.org> on 2008/12/03 01:40:44 UTC

[jira] Commented: (WICKET-1314) DateTimeField does not correct the timezone properly

    [ https://issues.apache.org/jira/browse/WICKET-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652628#action_12652628 ] 

Timo Rantalaiho commented on WICKET-1314:
-----------------------------------------

Ryan (or others), could you maybe explain in an easy way what impact does this have? I looked at the current code and the patch, but don't understand what effect does changing the timezone of the date being edited have (I'm just getting the same date value displayed before and after the patch).

> DateTimeField does not correct the timezone properly
> ----------------------------------------------------
>
>                 Key: WICKET-1314
>                 URL: https://issues.apache.org/jira/browse/WICKET-1314
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-datetime
>    Affects Versions: 1.3.4, 1.4-M3
>            Reporter: Ryan Gravener
>             Fix For: 1.3.6, 1.4-RC2
>
>         Attachments: DATETIMEFIELD.TXT, dtf.patch
>
>
> The DateTimeField has a DateTextField which uses a styledateconverter with timezone correction set to true which is not needed since the DateTimeField accounts for the TimeZone correction.  Another problem is that the DateTimeField only sets the timezone of the date (from local->client), causing the date to be corrected to the local time.  This should instead cause the local time to reflect that of the clients time.   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.