Form validation "on input change" - documentation misleading?

I’m trying to implement the validation of form fields and tried to get my head around how this form validation actually works (so thanks a lot for releasing the documentation for the new form validation feature!).

In my opinion, the common behavior of a form field validation is that once a user leaves the form field (on blur), the form validation checks if the input is valid (and indicates in case it’s not by displaying an error text). So, except for password fields, I’m not really sure what the use case is for the form validation type “on input change” in the current way it is implemented.

I went through the example that is shown in the WeWeb documentation here, and I realized that the shown example actually shows the problem with the current way the validation works:

In the example, the validation text (“Password must be at least 6 characters”) is shown once the user typed in at least 6 characters in the password field - which is the opposite of what would be expected. The validation text should only appear in case the user has not typed 6 characters (that’s why the validation should be done in my opinion on blur and not on input change).

Are there any plans to add the form field validation on blur? If not, what is the best way to implement the validation on blur? Of course it’s possible to implement a workflow for each form field on blur to validate the input and display an error text in case the validation is wrong, but what’s the use then of the form validation feature “on input change”? (for passwords, I get it, but besides that?)

Hi Julian, thanks for the feedback, the article is fixed. I think there are a couple of use cases for on change, for instance, to check if a username is available while typing. You can also use validation delay to create a “pause detection” that’s similar to blur in many cases. I will pass your feedback to the team, thanks again!