The input should be focused after the user clicks the clear button.

The DateInput rendering performance worsened in version 4.6.0 and the component renders more slowly. This is easily visible when there are multiple DateInputs on the page:

4.5.0: https://blazorrepl.telerik.com/mdPFuXFI02i7Ulbo52

4.6.0: https://blazorrepl.telerik.com/GdlbEXPe00IhfKWN29

When you check and uncheck the checkbox, the DateInputs appear more slowly with version 4.6.0.

There is also a Grid, which is commented out. If you show it, the virtual scrolling will exhibit a temporary freeze before rendering of the new rows - the user sees the loading skeletons for a second even after they have stopped scrolling.

This issue is for all date inputs when having a higher latency (physical distance between the server and the end-user) the value of the date inputs is not correct. 

Deleting a date segment clears the entire date and automatically focuses on the last date segment.

If you use the FloatingLabel, when you tab into the DateInput control, the cursor is set at the very end of the text of the date format. However, if you do not use the FloatingLabel, and you tab into the DateInput control, the placeholder text is selected.

Reproduction: https://blazorrepl.telerik.com/wQlvclOZ14jEKaXU38.

===

ADMIN EDIT

===

The report is initially opened for DateInput, however, it also targets the rest of the date pickers that are compatible with FloatingLabel.