Alain,
did you manage to test the "midnight problem"? )))
It's 2 AM in Moscow and just spent some time in Firebug and found out
that the problem arises on line 683,
var str = I8N._format(pattern, (loc ? date.getDate() :
date.getUTCDate()), "dd");
loc variable here is undefined, so str receives the result of
getUTCDate(), that is 1 day earlier. If you set focus in date control,
and click on another control once again, the date in the control will
become another day earlier and so on.
If you set a breakpoint there on line 683, you will see on callstack
that loc is undefined because of date.parse implementation (line 5818):
"parse" : function(value) {
return I8N.format(I8N.parseDate(value), "yyyy-MM-dd");
}
If you change it for
return I8N.format(I8N.parseDate(value), "yyyy-MM-dd", true);
the problem disappears!!
So my suggestion is to add ",true" to I8N.format call on line 5819.
However, I am not at all sure that this is the right way to fix the
problem, because I do not quite understand this code, so this is
definitely something that you should assess )))
Tank you in advance,
Regards,
Ivan Ponomarev.
On 20.01.2011 0:38, COUTHURES Alain wrote:
>
>> Every second time Calendar control tends just to remain on screen
>> after selecting date. This happens in Chrome, Firefox, ie7& ie8.
> I can't reproduce this issue. Can you please test this again with the
> latest SVN release? Could give me an external link??
>> Another problem with calendar: we live in time zone GMT +3 (Moscow)
>> If we try to work with form from 0 to 3am (yeah, sometimes we work at
>> night:))), then each exit from date control (by mouse clicking on any
>> other control) will increase date by +1.
> This sounds like a mismatch with Javascript functions and timezone. But
> I will probably have to wait till midnight myself to test it myself... ;-)
>
> Thanks!
>
> -Alain
>
>
|
