Blazor Date Input Bug: Why Visible UI State Can Silently Diverge from Model Data

A debugging case in a Blazor application revealed that a date field appeared correctly filled in the browser while the underlying .NET model property remained null, triggering a misleading validation error. The root cause was a mismatch between the native HTML date input's ISO wire format and a culture-aware component converter expecting a locale-specific short-date pattern. This silent divergence meant user selections were never actually bound to the model, and loading existing dates could render empty controls, risking unintended data loss on save. The fix adopted a date-picker component that unified its UI and binding contract, eliminating the format disagreement. The broader lesson is that UI visibility does not guarantee application state binding, and explicit ownership of formatting and parsing logic is essential at every field boundary.