Hi Philip,

Indeed if you are dealing with big data input having to use the mouse is not the most convenient way. However, the input supports keyboard navigation and pressing the left/right arrow will allow you to switch between day, month and year fields (you can test that in the Grid overview demo, I've recorded the video on that page).

If you type, for example, 1 for the month, the focus will still be at the month field to let you type one more digit for a valid two-digit month (10, 11 or 12). In such cases you can use the right arrow to navigate to the next field - the day in the demo(see video attached, I'm only using keyboard navigation, no mouse).

In terms of the issue you are facing with fast typing, it is most likely due to high network latency. I have tested it locally but the issue is not present. You can also test it locally to see for yourself. In the meantime, you may find this article helpful to also test your network latency.

You might take into consideration that the necessary latency value for best performance may vary depending on the user action - for example, a button click is a typically slower action than typing and will work fine even with higher latency. On the other hand, fast typing will require much lower latency value in order for the application to perform as expected.

When working with online applications, Server side Blazor might not be the best solution in certain cases - for example if the user is far away from the server or if they are using a VPN, firewall etc, the application will not deliver the best results. Therefore, it might be a good thing to consider switching to the WASM version of Blazor. Since the WASM Blazor application runs directly in the browser, this reduces the necessity of a constant connection with the server and thus providing faster online performance.

As for the users nationality and date formats, you might go for localizing your application - more information how to achieve that you can find in our Localization docs article.

Regarding the "pressing 0  in the DateInput deletes the date" bug - since we have a bug report already opened for it, I will mark this one as duplicate in order to keep the portal clean and properly keep track of the requests. You can follow the original post to be notified on a status change.

Note: As per our feedback portal status scheme, the "Unplanned" status indicates that this is a valid bug report not scheduled for implementation yet.

Regards,
Nadezhda
Progress Telerik