The problem comes because of the Daylight saving time change in this dates.
In some countries the clock is moving forward with one hour (or even 1.5 or 2 hours). So for example the "October 16 2011 00:00:00 AM
" does not exist as valid time.
For example if you are in Brazil:
In 15 october
you use GMT+2
time, and the first moment the time is:
11:59:59 PM on October 15
with no DST (UTC-3h)
And one moment later it gets:
October 16 1:00:00 AM with DST +1h (UTC-2h)
And since the October 16 00:00:00 AM
+1h does not exist(is not valid time), you can't select it in the DatePicker. The DatePicker itself selects the date with 00:00 hour.
You could manually change the selected time with one hour to 1 AM if you like. For example you could use this code:
function valueChanging(sender, args)
if (args.get_newValue() == "10/16/2011")
// 10/16/2011 for the given timezone will be auto-corrected to 10/15/2011 11:00 PM
// Then in DateInput only 10/15/2011 will be shown, so change it to 10/16/2011 01:00 AM to be parsed as 10/16/2011
//if you use DateTimePicker in the if statement check for "10/15/2011 11:00 PM"
args.set_newValue("10/16/2011 01:00 AM");
Please not that the code-above currently will not work,
and will work properly for the next release
. There was a bug in the DatePicker/DateTimePicker that was causing even 10/16/2011 01:00 AM to be parsed as 10/15/2011, because the date and time is parsed separately by design. The fix will be included in the next release, and you would be able to select the date properly.
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed