[
https://issues.apache.org/jira/browse/TAP5-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107843#comment-13107843
]
Robert Zeigler commented on TAP5-841:
-------------------------------------
For one, the patch you provided doesn't support IE < 9. That's a no fly for
me, at least... I still have apps that have to support IE 7...
For another, there's no test in your patch. To be honest, this is the part that
has put this ticket on the back burner for me. I've been investigating ways to
have an automated test where the server and client have a different timezone,
reliably, there's at least one option that I've found, but it's not... pretty.
If you can come up with a solution that supports IE >=7, and an integration
test proving the behavior, I will merrily apply your patch that same day. :)
> 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: Robert Zeigler
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
