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.
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.
### 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.