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. //
