[
https://issues.apache.org/jira/browse/TAP5-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747396#comment-13747396
]
Jochen Kemnade commented on TAP5-841:
-------------------------------------
This also affects 5.4. Paul's approach (transferring string representations
between the server and the client) will work fine regardless of client/server
time zones as long as we're talking about day precision only.
AFAICT, converting to milliseconds will only work if client and server have the
same time zone offset at the first instant of the date that is selected
(usually but not necessarily midnight), because that's what
DateFormat.parse(String with days precision) returns. This millisecond value
will only have the same String representation on the server and the client if
they have the same time zone offset at the respective instant.
I'd really like to have this fixed for 5.4. What can we do to make that happen?
Would it help to write a test that fails with the current implementation and
works with the patch? I have a rough idea how that could be done and would give
it a try if everyone's okay with that.
> DateField selects wrong date if client is in a different timezone than the
> server
> ---------------------------------------------------------------------------------
>
> Key: TAP5-841
> URL: https://issues.apache.org/jira/browse/TAP5-841
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: David Rees
> Assignee: Howard M. Lewis Ship
> Attachments: T5.3-DateField-Patch.txt
>
>
> This affects 5.0.18 and 5.1.0.5 in my testing.
> Situation is that if the server is running in a different timezone than the
> client, the DateField chooser will select the wrong date on the calendar.
> For example, if the server is running in "Pacific/Auckland" and the client is
> running in "America/Los_Angeles", Auckland is a "day ahead" of Los Angeles
> for most of the time and the bug is easy to reproduce.
> Right now it is 3:40PM Sep 8, 2009 America/Los_Angeles and 10:40AM Sep 9,
> 2009 Pacific/Auckland. If the date on the server to be displayed by the
> DateField is Sep 9, 2009, when you select the date chooser, Sep 8, 2009 is
> selected in the JavaScript calendar dialog.
> I found this message which seems to indicate that Howard thought it might be
> an issue - looks like he was correct:
> http://www.nabble.com/Re%3A-Tapestry-5.0.15-DateField-localization-problem--patch-included--p20033325.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
