Hi,

I have run into an issue when trying to input a date value where its parts contain a leading 0. The autoCorrectPaths option is set to false and I have specified a date format in my datePicker component. 

Reproduction:

1. open https://stackblitz.com/edit/react-wz6zocpe?file=app%2Fapp.jsx

2. try to input a date by typing 09, then 03, then 2025

Expected behaviour:

The date in the input field should be "09.03.2025"

Actual behaviour:

The date in the input field is "day.09.2000"

When my users are done typing in one date segment, I want the focus to pass to the next one automatically. 

In some cases, a null value is valid for the DatePicker. However, if the user types an invalid (or partial date) the value of the component is also null. In these two cases the null values must not be treated equally, but I have no way to understand which is which. 

It would be great if KendoReact had a `WeekRangePicker` component which behaves similar to the native html element input type="week"

I use the DatePicker extensively in our application as people are entering in weather data. They often want to change the date by a day or two, so they find it annoying to open up the whole calendar to go back a single day. I think that the ideal UX would be to have the equivalent of the Spin Buttons on the DatePicker that exist on the DateInput. So, there would be the calendar for the date picker and the spinners so users can choose what works best for them.

Hello,

We've been experiencing a weird behavior with the date picker element. We wanted to have an auto advancing cursor that moves from date -> month -> year without the user having to manually press the arrow keys.

We based our solution off this previous method in your JQuery element. However the React element has some buggy behavior when it comes to updating existing date values in the input that makes this method impossible. (the functionality works correctly in the JQuery version of the library, just not React)

When updating an existing value in the box from a single digit value (e.g. 01, 02, 03, 04, but not 10, 11, 12) instead of overwriting the existing value it appends the new number the user entered. For example, if a 01, is in the box and the user types 2 it becomes 12, when it should have become 02.

This can be especially confusing for the user when working with named dates (e.g. "Jan", "Feb",  "Dec", etc) since they do not see the numbers involved. If the user is updating Jan, and they press 2. It should update to Feb not Dec...

I've attached a GIF of the problem below as I've described