RadzenDatePicker component issue

Radzen.Blazor Components
1

Hi Team

I’ve noticed that when using RadzenDatePicker in a form with validators (e.g., RadzenRequiredValidator), manually typed dates are not committed to the model until the field loses focus. This causes validation to fail if a user types a date and immediately submits the form without leaving the field.

Currently, the recommended workarounds are:

  • Using a custom wrapper with a TryCommit() method to parse manual input.

  • Handling input via JavaScript to update the model in real-time.

However, these approaches require additional code and are not ideal for large projects.

I would like to request a built-in property or behavior in RadzenDatePicker to commit manual input immediately on submit or on input, so that validators can reliably work without extra code.

Thank you for considering this enhancement — it would greatly improve usability and reduce boilerplate code for forms using RadzenDatePicker.

2

It’s possible to add Immediate property similar to other components like Numeric, TextBox, etc. however there’s a catch. Unlike a plain text box, date parsing on every keystroke is tricky — partial input like 03/1 would fail to parse mid-typing. The implementation might need to debounce or silently ignore parse failures until a valid date is typed - it might clear the bound value on every invalid intermediate keystroke. I’ll check what we can do!

3

@enchev Thanks for your attention.

I researched this issue and also reviewed how other libraries handle similar scenarios. One possible approach could be: when the user types input, the component attempts to parse it, and the bound model value is updated only if the parsing succeeds.

If parsing fails (for example, during partial input like 03/1), the component can simply ignore it until a valid date is entered.