tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Eynon (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (TAP5-841) DateField selects wrong date if client is in a different timezone than the server
Date Sun, 18 Sep 2011 12:50:10 GMT

    [ https://issues.apache.org/jira/browse/TAP5-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107138#comment-13107138
] 

Steve Eynon edited comment on TAP5-841 at 9/18/11 12:48 PM:
------------------------------------------------------------

I've attached a patch for T5.3, but I dare say it also works for T5.2.6. 

It looks bad that T5 still doesn't have a working Date component. As a fix for this is only
a couple of lines I'm very surprised this JIRA is still out standing!

(Oh, and before it's mentioned, no there are no unit tests in the patch - trying to get a
working dev env for Tapestry was taking too much time. Therefore the patch is just intended
for users to Munky Patch their T5 jar.)

      was (Author: slimerdude):
    I've attached a patch for T5.3, but given this JIRA has not been touched for 2 years I
dare say it also works for T5.2.6. 

As a fix for this is only a couple of lines it looks bad that T5 still doesn't have a working
Date component. I've never deployed to a prod server in the same country / time zone as the
users so I can't believe this issue is still out standing!

(Before it's mentioned, no there are no unit tests in the patch - trying to get a working
dev env for Tapestry was taking too much time. Therefore the patch is just intended for users
to Munky Patch their T5 jar.)
  
> 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

        

Mime
View raw message