Bug report

The close event of a DateTimePicker with componentType: modern does not provide reference to the view

Reproduction of the problem

1. Run this dojo
2. Open and close the DateTimePicker
3. Note e.view is undefined

Expected/desired behavior

The event data of a DateTimePicker with componentType: modern should provide reference to the view

Environment

• Kendo UI version: 2022.3.913
• Browser: [all]

Since R1 2022, the setOptions method re-enables a disabled widget.

Dojo

https://dojo.telerik.com/aqazivIk 

Hi Kendo Team,

After we updated to version 2022.2.301 we decided to modify our theme by compiling the Metro theme from the source files and adjusting some of the variables provided.

When checking on the styles of the date-time-picker we noticed that the focused column of the time picker would not be highlighted anymore. Also the title would not get the darker color it had in the previous version (see attached image)

We noticed that in v2022.2.301 the focus class has changed from 'k-state-focused' to 'k-focus' (see inspector screenshot)

The styles in the files 'web/common/inputs.less' and 'web/type-metro.less' on the other hand still refer to the class .k-time-list-wrapper..k-state-focused to style title and the ::before and ::after elements that define the background color.

We will add styles to our custom file to correct this. The question for future updates would be though, which class will be the preferred one to keep.

Thanks,

Markus

The Timepicker portion of Date/Timepicker is showing an odd border and the highlight is slicing that border in half when hovering/clicking within the timepicker.  I looked at the timepicker only control, and this border is not showing.

I am attaching the 2 the snippets from dojo.telerik.com for each of the 2 controls to show the display difference.

Hi,

We are using DatePicker and DateTimePicker with DateInput.

Since Kendo UI 2021 R1 the DatePicker is showing the DateInput mask when the value is null. The DateTimePicker behaves correctly.

I've prepared an example. The value is set to null manually here, but in our code it is set via MVVM binding. 

https://dojo.telerik.com/OcaVaWoX

Reproduce:

1. Select Version Kendo 2020 R3: The DatePicker and DateTimePicker are both empty. That's the expected behavior.

2. Select Version Kendo 2021 R1: The DatePicker now incorrectly shows the DateInput mask, the DateTimePicker shows the empty picker correctly.

Best regards

### Bug report

When the Kendo UI DateTimePicker widget with componentType set to 'modern' is used in the filter menu of the Kendo UI Grid and the "Set" button is clicked, the form is submitted automatically.

### Reproduction of the problem

1) Set filterable.ui to be a DateTimePicker with componentType: modern;

2) Open the filter menu. Choose a date from the picker and click "Set";

3) The form is automatically closed/submitted.

A Dojo sample for reproduction (the 3rd column of the grid): https://dojo.telerik.com/ANEFExOC

### Expected/desired behavior

The form should not be automatically closed/submitted.

### Environment

* **Kendo UI version:** 2021.1.119
* **jQuery version:** 1.12.4
* **Browser:** [all]

Bug report

When using the readonly method for the Kendo UI DatePicker when toggling to remove the readonly attribute, the aria-readonly attribute remains.

Reproduction of the problem

1. Go to this dojo.
2. Inspect the DatePicker element.
3. Toggle readonly on and off for the DatePicker.

Current behavior

The aria-readonly attribute is still included in the Kendo UI DatePicker.

Expected/desired behavior

The DatePicker's readonly method should work like the DateTimePicker's method.

Environment

• Kendo UI version: 2021.2.511

Dear Kendo UI team,

I have experienced an issue with the Kendo UI datepicker when accessing it with a screenreader on the Kendo UI Vue preview page (https://www.telerik.com/kendo-vue-ui/components/dateinputs/datepicker/):

In the month/year view, if I change the selection, the selected date (from the original view before "zooming out" into the month/year view) is read out.

Expected behaviour: The currently selected month/year should be read out.

Steps to reproduce:

• Start a screenreader (I have tried NVDA and JAWS).
• Focus on the calendar, open it.
• Change the view to the month/year view by using Ctrl+Arrow Up.
• The focus is now on the month/year corresponding to the current date.
• Change the selection by using one of the arrow keys.
• No matter the current selection, always the (whole) current date is read out.

Software versions used:

• Browsers:
  • Chromium 77.0.3865.75
  • Microsoft Edge 44.18362.449.0
• Screenreader (always initial configuration):
  • NVDA 2019.1.1
  • JAWS 2019.1906.10 ILM
• OS: Windows 10, latest updates
• Keyboard layout: German

Furthermore, it seems to me that with Microsoft Edge in combination with JAWS I cannot open the month/year view, maybe because of a conflict of keyboard event handlers between the component and JAWS. Also the escape key has no effect, it does not close the datepicker.

The issue also occurs for the original jQuery version.

Thanks for your support.

Kind regards,

Andreas Schütz

Bug report

If the user opens the Kendo UI DateTimePicker with a componentType of "modern", then selects set without any modifications, it will select today instead of what is in the input.

Reproduction of the problem

1. Go to this Progress Kendo UI Dojo.
2. Open the DateTimePicker and select set.

Expected/desired behavior

The value in the input should remain set as the Kendo UI DateTimePicker's value.

Environment

• Kendo UI version: 2020.3.1118
• Browser: All

Bug report
In "modern" style with 24h format, it's not possible select 00 hour but only 24 

Reproduction of the problem
Open below Dojo:

https://dojo.telerik.com/AVUPahuS

Open TimePicker and try to Select 00:00

Current behavior
There is no 00:00

Expected/desired behavior
User shall be able to select 00:00 as it is in non-modern type

Environment
Kendo UI version: 2020.2.617 and above
jQuery version: x.y
Browser: [all]

Hi, 

When I'm set ngModel directive to the component, the messages are gone when my initial model value is null, empty string or undefined. Is there a way to prevent this behavior? I want to show the messages of the dateInput if the model does not have a valid date.

Here is an example of this. https://dojo.telerik.com/UvAWurud/5. You will be able to see the messages briefly displayed, but then they go away.

Thanks!

Hi,

Today I noticed a wrong behavior with the dateInput.

After the component is initialized with a predefined value, I can't change day part value, the component does not accept them.

In the next dojo you can see if I try to change directly day value, it marks it as invalid value. I need to change it with arrow keys before to accept any value.

https://dojo.telerik.com/UlEDizoW

Maybe I'm missing something?

Thanks!

I was able to duplicate an issue I found when we upgraded to the latest Kendo UI for jQuery release. The DatePicker is not working correctly when the kendo namespace, kendo.ns, is set. I was able to duplicate it using the MVVM demo example for DatePicker. The month is no longer displayed and clicking on the Month to zoom out in time stops working as well. I have not checked what other functionality is not working. I do know the parsing is working properly as well as formatting.

I have two datetime picker to select a datetime range.

The max value of end datetime picker must be the 00:00 of a given day (that is only 00:00 of the given day must be selectable).
The min value of end datetime picker depends on the selection of start timepicker.

Hence I need to dynamically change the minimum value of end datetime picker while mantaining the max value to 00:00 of the give day as show in the following dojo link:
https://dojo.telerik.com/IFAWOrax
(based on https://demos.telerik.com/kendo-ui/datetimepicker/rangeselection)

But when you select a different hours from 00:00 on the start datetime picker, the max value of end datetimepicker is not matained.

Bug report

Current behavior
Component type does not apply in MVVM DateTimePicker

Dojo: https://dojo.telerik.com/eKALEfaN

Expected/desired behavior
Modern component type shall be applied

Current workaround:

Dojo https://dojo.telerik.com/OZaZaDaJ

Environment
Kendo UI version: 2020.2.617
jQuery version: x.y
Browser: [ Chrome XX ]

Creating a timepicker with a min value on a DST start day (e.g. March 10, 2019), before the start time, causes the drop down to options to loop over pre-DST start times:
12:30 AM, 1:00 AM, 1:30 AM, 1:00 AM, 1:30 AM, 1:00 AM....

Expected: Time options should continue through the day:
12:30 AM, 1:00 AM, 1:30 AM, 2:00 AM, 2:30 AM, 3:00 AM....

I noticed the error originally in version "2018.3.1017", but it is still happening in "2019.1.220".

https://dojo.telerik.com/ayamEFuZ/4

<input id="timepicker" />
<script>
    $(document).ready(function () {
        // create TimePicker with broken drop down picker options
        $("#timepicker").kendoTimePicker({
            min: new Date(2019, 2, 10, 0, 30)
        });
    });
</script>

Actual behavior:

User uses down key or mouse scroll to change the time. A 00:00 hour is set instead of chosen hour on blur.

Expected behavior:

A value chosen by user remains selected. It's not changed by the timepicker.

Additional Context:

This problem occurs only when picker.enable(true) is called after component creation and user uses down arrow / mouse scroll to get to the the 'previous' day. When no .enable method is called everything works fine. Please see attached code snippets and gifs.

Dojo link: https://dojo.telerik.com/OZEDuFEg

Bug can be reproduced using the following code snippet:

 $(document).ready(function () {
    // create TimePicker from input HTML element
    var picker = $("#timepicker").kendoTimePicker({
            dateInput: true,
            format: 'HH:mm'
        }).data('kendoTimePicker');
    picker.enable(true)
});

Removing 

picker.enable(true)

fixes the issue