In a filter input field I had one blur event
to fix a entered date string.
It wasn't called if the users hit "Enter" instead of cliking the Filter button or hitting TAB which
would cause a blur event.

T. Tsonev asked me to post this to "UserVoice portal":
Maybe an event that is triggered before attempting to read the value from the input.
This will consolidate both handlers in your case.


Below are the two handlers to fix an input field if a blur or Enter key is done/hit:

---

If an input field is changed and the user does a blur (TAB or clicks filter button) after
entering a date
or
hits the enter key without doing a blur.
the FixDate function is called and input field is changed
before the filter popup is submitted
and the Filter works if a date like this is entered:
11/9/2004 0:0
FixDate canges to:
11/9/2004 12:00 AM.

Below is the code I changed:
See the sections with "Fix "
comments.

Maybe they need a on "blurOrEnter"
event so you don’t need to make two tests?  (((, or an event that is triggered before attempting to read the value from the input)))
...
               // Fix - Modified to call a FixDate function.
               // Test for a blur (ie: click or tab to another widget and leave the input field)
               // NOTE: blur doesn't happen when the enter key is hit
               $("[data-role=datetimepicker]").on("blur", function()
               {
                    var element = $(this);
                    FixDate(element);
               });
     
               // Fix - Modified to handle the "Enter" key
               //       and call the FixDate function
               //       to modify the input field from "11/9/2004 0:0" to 11/9/2004 12:00 AM"
               //       before the form is submitted.
               //       This makes the filter work when the enter key is hit
               //       which doesn't cause a blur to happen.
               $("[data-role=datetimepicker]").on("keydown", function(e)
               {
                    // Test for Enter key
                    if (e.keyCode == 13)
                    {
                         var element = $(this);
                         FixDate(element);
                    }
               });
          }
     });

     // Change the date in the filter input field by using 
     // Datej Date.parse.
     // This will change strings like: "0:0" 
     // To: "1/29/2015 12:00 AM"
     // and allow the filter to work
     function FixDate(element) 
     {
          // Get element for datetimepicker
          //var element = $(this);
          // Get widget for datetimepicker
          var widget = element.data("kendoDateTimePicker");

          // See if element has changed
          if (element.val())
          { 
               // Set Text of widget to a Datejs string date from the elements text
               // IE: 11/9/2004 0.0 will be 11/9/2004 12:00 AM
               widget.value(Date.parse(element.val()));

               // Fix by T. Tsonev 01/26/2015
               // make a change happend so new text is used.
               // ie: Use "11/9/2004 12:00 AM" instead of "11/9/2004 0:0"
               widget.trigger("change");
          }
     }

...

---

The current date time and date-time pickers don't allow for scrolling the data using the mouse scroll. 
This functionality is available in ajax controls this makes a mix web site not consistent in behavior of controls.

DatePicker should let developer decide if the chosen day of the month should be persisted from month-to-month.

By default the DatePicker remembers the day of the month the user has selected, and that day gets styled differently even when the user navigates away to a different month: the user selects January 12th and then navigates to August, and the 12th day of August is styled differently too.

But there are many use cases for a DatePicker where it is not appropriate behavior to remember the previously selected day of the month when the user navigates to a different month. Remembering the day can actually make things confusing for the user in applications where this behavior is not the right behavior.

date picker should allow read only of text box

For the datepicker control, it would be great if it could support relative values for the min and max range like the jQuery datepicker does.  For instance, you can set minDate: 0, which is today.  Or you can say maxDate: "+6M" for a max date of 6 months from today (as in their documentation: https://api.jqueryui.com/datepicker/#option-maxDate).  These generic expressions make it much easier to set restrictions.

when mouse click in a kendoDatePicker, control will auto choose date part at clicked position, and we can use left and right arrow to go to another date part, use up and down arrow to cycle through all possible value of that part, or input number (month name in the case) directly instead

I'd like to be able to specify a custom date in the datepicker footer rather than "today".  In financial end of day applications you often want to select the previous business day e.g. the "close date".

Need a feature  to restrict the days to be displayed in the Kendo UI datetime pickers control.

 For example .   I want to only display say  dates than falls only on Thursday and Sunday  where users can select on that dates and the other dates to be disabled or invincible.

 I want to have a flexibility to change it to other days as well.

Add the option to be able to highlight today's date in calendar and date pickers.

Mobi scroll already provides this kind of selection (http://demo.mobiscroll.com/calendar/calendardatetime/#)

but mobiscroll does not offer the full support of a schedule that kendo UI does. But oh how sweet it would be if Kendo also provided support for scrolling. 

As far as UX/UI is concerned picking a date and time via slot machine scrolling style is much easier to do on a mobile device.

Thanks!

because dateTimePicker can show weekNr now, if it is possible to enable select whole week ( or select weekNr), Thanks

Add the feature to be able to walk through date, hour, and minute selection in a stepped fashion, similar to the functionality of this DatePicker:

http://www.malot.fr/bootstrap-datetimepicker/demo.php

The gist is to first allow for day selection. Then, with the popup still open, give the user the ability to select the hour of the day, and finally the particular minute of that hour.

Have the time drop down function kind of like normal drop downs, where they don't filter, but will jump down to the time you start typing after opening the drop down like the drop downs do when you start typing after opening them.

I get people complaining at the length of lists for timepicker inputs, especially if using small minute intervals.
How about an alternative input mode that allows for faster and simpler input.

This method is great - visual, intuitive and quick.
http://www.youtube.com/watch?v=lYxxyPvOHyA

Few others out there all with pros and cons

DateInput doesn't support fuzzy dates. (Where day/month/year are optional) This is useful in order entry applications where the developer doesn't have control over what information is available from customers and information supplied is inconsistent.

The DateInput controller could have an option to read/submit formatted strings or some kind of strongly typed DTO so that given parts of the DateInput initialize as blank/null.

Currently the disabled date function only make the dates disabled, but if you are using the component as a month/year picker through the "depth" property you would also like the months/years to be unselectable if the whole month is included in the disabled date period.

I want the datetimepicker to pull from the database if a value exists, show nothing if it doesn't, and get the current date and time when user clicks on the calendar icon.   It doesn't get the current time.  It shows midnight.  I can get the datetimepicker to default to today's date (on display) and current time if I don’t try and pull a value from the database.

I noticed that the time picker would not parse a 3 or 4 digit time w/ am/pm (that doesn't have a ":" separator) even though there wouldn't be any ambiguity based on the parseFormat array.  I was told that the picker doesn't officially support any time parsing that doesn't contain a colon and if some work without a colon it is by chance.

This vote would be for more thorough format parsing on the picker controls.  The ones I specifically noticed were failures to parse "hmmt", "hmmtt".  See this ticket for more info and a dojo example.

https://www.telerik.com/account/support-tickets/view-ticket?threadid=1164654

An alternate header with Month and Year Dropdowns would be helpful on the DatePicker

The editors do support inline footer's but you can't use an external footer template yet.

Example template:

<script type="text/template" id="datepicker-footer-template">

    "Today: #:kendo.toString(data, 'yyyy-MM-dd')#, Week: #:kendo.recurrence.weekInYear(data,kendo.culture().calendar.firstDay)#"

</script>

Suggestion to add a footer-template configuration option like this:

<input name="Date" data-role="datepicker" data-bind="value: Date" data-format="yyyy-MM-dd" data-week-number="true" data-footer-template="datepicker-footer-template"/>

Jan