tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-841) DateField selects wrong date if client is in a different timezone than the server
Date Wed, 29 Mar 2017 12:51:41 GMT

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

Hudson commented on TAP5-841:

FAILURE: Integrated in Jenkins build tapestry-trunk-freestyle #1611 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/1611/])
TAP5-841: don't try to interpret date strings when formatting/parsing (jkemnade: rev 42e550da492a26b7685ebfe1f8604d9e0b3e00b2)
* (edit) tapestry-core/src/main/java/org/apache/tapestry5/corelib/components/DateField.java
* (edit) tapestry-core/src/main/coffeescript/META-INF/modules/t5/core/datefield.coffee

> 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.4,
>            Reporter: David Rees
>              Labels: desired_for_5.5
>             Fix For: 5.5.0
>         Attachments: T5.3-DateField-Patch.txt
> This affects 5.0.18 and 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 was sent by Atlassian JIRA

View raw message