When the dateinput is created using data-role attribute and the unbind method is used to unbind the component an error is thrown.
Uncaught TypeError: Cannot read properties of undefined (reading 'kendoBindingTarget') is thrown in the console
No error should be thrown when destroying dateInput component.
Add a hidden input to store the current value in it at all times, and a visible display input that has the month/day/year or current value displayed in it; it solved all of the issues and is currently implemented on numerous other Kendo form input controls.
This will make the DateInput compatible with JQuery Unobtrusive Validation.
I would like to request the functionality to configure the format of the DateInput's messages. This would help remove any symbols used when the value is set in the DateInput. For example, here is a Progress Kendo UI Dojo which shows a TimePickers DateInput with a colon in the message.
The DatePicker widget does not focus the input element when the calendar icon is clicked. Because of that, validation errors are persisted even when the value of the input has been filled out correctly. The input needs to be manually focused and then unfocused to get rid of the validation message.
This behavior can be observed on the following demo page:
The demo should be viewed in mobile mode.
Currently, when the "dd/MM/yy" format is used and the "year" part is populated with a two-digit number, the value of the widget converts to "01/01/00" which is 1st of January 1900 (the default min value for the DateInput).
The widget assumes that the year is "00xx". However, we should have the option for setting the century to the current one, hence, having the first part of the year as "20xx" or "19xx".
Example for the current behavior of the widget:
I have noticed some weird behaviour when using the SwiftKey keyboard on Android.
- Install SwiftKey keyboard and enable
- browse to https://demos.telerik.com/kendo-ui/dateinput/index in chrome for android
- Select year component of date input control
- type 1 - year shows as 0001 - correct
- type 9 - year shows as 0019 - correct
- type 7 - year shows as 0009 - incorrect
- type 5 - year shows as 0019 - incorrect
All the other keyboard i have tried work as expected, i appreciate that this is a non standard keyboard on Android however it is a widely used one and works as expected when typing 1975 into any other app / control on the device.