Any updates on this pr @ericsoderberghp @ShimiSun ?

Apologies for such a long delay in responding to this. Thanks for the new story. I tried interacting with it in the following manner:

• click on the Blur field
• tab to the Submit field - no validation is shown for the Blur field, I would have expected the "required" validation to be shown
• tab to the Change field - no validations are shown, which seems correct
• shift tab back to the Submit field - no validation issues are shown for the Change field, I was expecting it to show "required"
• shift tab back to the Blur field - no validations are shown, which seems correct
• type "a" - the "must be >1 character" validation shows up, this seems like it is being shown based on a change rather than a blur, which doesn't seem correct.

I didn't attempt to sift through the code to pinpoint where the issues might lie. But, I figured this testing might be helpful to start with.

Thank you for pointing out these issues.

• I have resolved the "required" validation not showing on "blur" validateOn value.
• For the same bug on the "onChange" validateOn value, it is currently exists on live deployment too https://storybook.grommet.io/?path=/story/input-form-validate-on-change--validate-on-change. I am not sure if this is something, we should take a look into more. If so, please tell me.

One more thing I notice, Suppose, there are 3 Form fields wrapped around the form component, if the user specifies the Form level validate ="change" prop and also specifies the Form Field level validateOn="blur" prop only on 1 form field, we would expect that the other two form fields automatically gets change validation behaviour. Is this the correct behaviour ?

@ericsoderberghp It's been a long time since this pr is reviewed. I will really appreciate your's and Grommet maintainers efforts to take some time out of your busy schedule to review this pr.

One more thing I notice, Suppose, there are 3 Form fields wrapped around the form component, if the user specifies the Form level validate ="change" prop and also specifies the Form Field level validateOn="blur" prop only on 1 form field, we would expect that the other two form fields automatically gets change validation behaviour. Is this the correct behaviour ?

Apart from this scenario, I don't see any issues with this pr. Please, let me know if you find any unexpected behaviour. Thanks :)
cc @ShimiSun

Hi @g4rry420 sorry for the long delay here. Thanks for reaching out to get some eyes on this again! I think this is super close to the finish line.

The behavior looks good to me, I'm in the process of digging into the code a bit more to make sure things look good there.

One more thing I notice, Suppose, there are 3 Form fields wrapped around the form component, if the user specifies the Form level validate ="change" prop and also specifies the Form Field level validateOn="blur" prop only on 1 form field, we would expect that the other two form fields automatically gets change validation behaviour. Is this the correct behaviour ?

Yes, I think that is the correct behavior. If validation is defined at the FormField level then that should override the Form level but only for that field. The other fields should align with the Form level validation.

@jcfilben Above discussed behavior is also implemented. Please, let me know if you see any issues :)

@jcfilben Above discussed behavior is also implemented. Please, let me know if you see any issues :)

Tested this out and storybook and so far it is looking good! Still working my way through the code. In the meantime I think it would be nice to have some unit tests for this.

I think the new story should be omitted from Chromatic snapshot evaluation, since it's there just for interaction. We can take care of this post-merge.