Possible issue with form binding?

[webprofusion-chrisc]

Although I'm unable to recreate the problem myself one of my users seem to be having recurring issues with our New User signup form (which uses Blazor Server, net9.0 rc 1, self-contained deployment) saying they haven't filled it out properly (in particular email confirmation and password confirmation) when they insist they have. Two users at the same org report the same problem, so I suspect a particular browser or extension.

The code in question literally validates by checking the model values match, so it's not fluentvalidation etc.

Has anyone seen any issue with forms not reliably binding to models? I've tested in multiple browsers but have yet to recreate the problem, it could be as simple as interacting with the form in a particular order or using/not using tab etc.

[webprofusion-chrisc]

Perhaps it's related to this note in the docs (also note the typos in the text), I'm using simple generic names like "confirmed-email" for Name instead of "Model.PasswordConfirmation.ConfirmedPassword", not sure if that matters:

Note: When using the input components in SSR mode, be sure to assing a value to the Name property otherwise the enhanced form functionalty will not work. In contrast to the standard Blazor input components a name is not automatically being generated. Also, the Name needs to be prefixed with the model name (i.e. Model.Username).

[webprofusion-chrisc]

False alarm, I had a bug where we remembered their last validation result so if validation previously failed then it would fail again for the same reason.