I am experiencing problems with the k-ng-model binding on the DateRangePicker.
I made a Dojo example. Scenario and working / not working example included.
Reproducable in the following Dojo:
Open the daterangepicker and make a selection, for example 10th of December to 15th of December(10.12 - 15.12).
Open the daterangepicker and make another selection 12th of December to 17th of December(12.12 - 17.12).
Only the 17th is selected instead of the entire 12-17 range.
I'm observing this issue with the Demo version of the DateRangePicker: https://demos.telerik.com/kendo-ui/daterangepicker/index
The End Date is not set and the Start Date changes to the selected End Date.
I've implemented the DateRangePicker in our software and I noticed that the selection of the DateRangePicker has a slide different behavior to the Angular DateRangePicker.
This behavior is also reproducible in the demo website.
Select a range. Alter range to the new values. First, update '03-11-2019' -> '04-11-2019'. Second, update '09-11-2019' -> ''
Start date: 03-11-2019
End date: 09-11-2019
Now I want to update this range to:
Start date: 04-11-2019
End date: 16-11-2019
Start date: 16-11-2019
End date: null
When I select the start date, it's updated as expected (04-11-2019) but selecting the new end date (16-11-2019), sets the a new start date instead of the end date. As described by the result values.
Dear Kendo Support Team,
we are using Kendo UI in our ASP.NET MVC application. We want to remove the values from DateRangePicker. The dates are removed from inputs but the calendar keeps the previous value highlighted when we move back and forth between the months.
Example code: https://dojo.telerik.com/ATuyAWuF/3
The change event of the DateRangePicker fires three times every time you change an input field.
This is a regression in Kendo v2019.2.514
The change event fires three times on every input change, for a total of six.
The change event should only fire once when a date is selected.
### Bug report
### Reproduction of the problem
_(bug report only)_
When start and depth are configured on a DateRangePicker, users are unable to select а range.
### Expected/desired behavior
The expected is users to be able to select range as it is currently in DatePicker.