I really like this feature of the DatePicker but I have a gripe.
I am working with British (en-GB) date format - day/month/year. If I enter the following string into the date input box, '12/32/2011' then this is seen as an invalid date string. If however I enter the following erroneous date string '12/13/2011'(meaning the twelth day of the thireteenth month of the year), the built-in validation mechanism seems to treat it as if it had been entered in en-US format (meaning the thirteenth day of the twelth month) and redisplays it as '13/12/2011'. It does not see this date string as invalid.
So, to catch this type of input error I have to validate the input string using the DateInput's client side 'OnValueChanged' event.
It would be so much nicer if Telerik could provide a user option which allowed me to select either the current 'corrective' behaviour or a 'strict' behaviour that trapped any inconsistencies in a date string.
Rgds
Len Jones
I am working with British (en-GB) date format - day/month/year. If I enter the following string into the date input box, '12/32/2011' then this is seen as an invalid date string. If however I enter the following erroneous date string '12/13/2011'(meaning the twelth day of the thireteenth month of the year), the built-in validation mechanism seems to treat it as if it had been entered in en-US format (meaning the thirteenth day of the twelth month) and redisplays it as '13/12/2011'. It does not see this date string as invalid.
So, to catch this type of input error I have to validate the input string using the DateInput's client side 'OnValueChanged' event.
It would be so much nicer if Telerik could provide a user option which allowed me to select either the current 'corrective' behaviour or a 'strict' behaviour that trapped any inconsistencies in a date string.
Rgds
Len Jones