Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tapestry.apache.org
Date: Tue, 1 Jul 2014 06:54:24 +0000 (UTC)
From: "Jochen Kemnade (JIRA)" <jira@apache.org>
To: commits@tapestry.apache.org
Message-ID: <JIRA.12435162.1252449785347.78745.1404197664401@arcas>
In-Reply-To: <JIRA.12435162.1252449785347@arcas>
References: <JIRA.12435162.1252449785347@arcas>
Subject: [jira] [Commented] (TAP5-841) DateField selects wrong date if
 client is in a different timezone than the server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jochen Kemnade commented on TAP5-841:
-------------------------------------

The only thing that prevents me from getting started on this is that I'm not sure about that {{LocalDate}}-like class. Given that we'll probably switch to Java 8 after Tapestry 5.4, that class would virtually be deprecated from the start. Also, if we really call it {{LocalDate}}, there would be two Tapestry classes with that name (there is also a LocalDate component in 5.4). Of course, we could call it YearMonthDay, like JodaTime's old implementation.
But DateField could also use a plain ISO 8601 string internally and Tapestry could provide coercions from and to {{Date}}.

> 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, 5.1.0.5
>            Reporter: David Rees
>         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 was sent by Atlassian JIRA
(v6.2#6252)