[ https://issues.apache.org/jira/browse/TAP5-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096329#comment-13096329 ]
Robert Zeigler commented on TAP5-841: ------------------------------------- I haven't tried the fix yet, so no comment on the XMLInputFactory2 business, other than it sounds like a classpath problem, unrelated to this bug. The modifications made to the DateField for TAP5-1409 have changed the behavior related to this bug somewhat. I still observe the bug, but given the code: .java: @Property @Persist private Date date; .tml: <t:form> <t:datefield t:id="date"/> <t:submit/> </t:form> You /observe/ the incorrect date being set the very first time (eg: click on the 3rd, and see the 2nd). If you then change the date back to the third, it stays the third. /However/, at that point, it is the 3rd in the /server's/ locale, rather than the user's. That's probably not the desired behavior... > 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 > > 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