Hi everyone,

I have amended the title so it better reflects what we would do. It is actually related to the post by Rick - typing with the keyboard should focus the next segment every time a valid input has been achieved. To take the provided example - if you write "11" for the month, focus should move to the next segment.

I must also note that the MVC date picker does not have this behavior.

Regards,
Marin Bratanov
Progress Telerik

Hi Kyle,

Let's keep this discussion here so we can determine what behavior you expect from the component.

To begin with, there is an issue with writing the years right now, and you can Follow it here: https://feedback.telerik.com/blazor/1456610-unexpected-years-validation-behavior-on-keyboard-input. It breaks the typing at the moment, so you won't be able to experience the full potential of the Blazor date input. In short - you can use the arrows to move left and right between the date/time segments to change them. You can also use the up/down arrows instead of typing numbers or day/month names. The ability to keep typing in the current segment is a conscious choice in our Blazor component.

On my end, both components behave in, essentially, the same way. You have to replace the current text with the new one. In the MVC demo, merely typing numbers does not update the date. I am attaching here a short video that illustrates what I see and what I expect so you can compare and confirm if I am missing something.

Once we establish a baseline and a working example of the desired behavior, we will be able to determine how to proceed.

Regards,
Marin Bratanov
Progress Telerik