In new corelib\components\DateField one can find:
JSONObject onParse()
{
...
response.put(RESULT, date.toString());
...
}
For my timezone it returns: "Mon Sep 01 00:00:00 EEST 2008", but then in
datefield.js it tries:
var resultHandler = function(result)
{
var date = new Date(result);
date would have Invalid Date value, and the whole calendar popup would show
up ruined.
I tried messing with FireBug in console and it looks like EEST timezone name
is a problem, if I put GMT+3 in it then javascript engine in my FF would
parse that date.
Possible fix would be changing date.toString() to date.getGMTString() -
which is deprecated long time ago.
--
View this message in context:
http://www.nabble.com/Tapestry-5.0.15-DateField-localization-problem-tp19723586p19723586.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
