Sorry, I need to clarify the steps to reproduce:
If load the page with a null value, the first selection from the widget
works fine (ie 01/07/2011).
If you use the widget again to select the same date, it doesn't work,
the field now contains 02/07/2011.
Regards, Paul.
On 12/07/2011 12:44 PM, Paul Stanton wrote:
Hi all,
Tapestry 5.1...
I've run into a problem with the datefield component and am about to
look into patching it, but if anyone can offer some advice it would be
appreciated.
Our server is running in "Australia/Brisbane" timezone and some of our
clients are in the "India/Mumbai" timezone.
The problem is, when the clients select July 1, the input field is
populated with July 2. Selecting July 1 again results in July 3 in the
input field.
If this sounds familiar, please reply.
Regards, Paul.
//
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
