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
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.
-
You can reply to this email to add a comment to the issue online.
