We have moved back to PrimeVue version 4.2.5 as the Form validation in 4.3.2 (and in 4.3.1) does not behave nicely in our forms. The difference can be demonstrated with this demo on Stackblitz The example can be run with both version 4.2.5 and 4.3.2 by changing the versions in package.json.

The form contains two Selects. Selecting a value from the first list updates the options in the second list.

In Primevue 4.3.2 the second Select becomes invalid immediately after picking a value in the first list. This means the user will be confronted with invalid fields even before being able to enter a value or submitting the form.

Primevue 4.2.5 behaves much better in this respect.

Is this a bug? Is this intended behaviour? If so, how do we stop needless validations of inputs the user hasn't touched?

We have moved back to PrimeVue version 4.2.5 as the Form validation in 4.3.2 (and in 4.3.1) does not behave nicely in our forms. The difference can be demonstrated with this demo on Stackblitz The example can be run with both version 4.2.5 and 4.3.2 by changing the versions in package.json.

The form contains two Selects. Selecting a value from the first list updates the options in the second list.

In Primevue 4.3.2 the second Select becomes invalid immediately after picking a value in the first list. This means the user will be confronted with invalid fields even before being able to enter a value or submitting the form.

Primevue 4.2.5 behaves much better in this respect.

Is this a bug? Is this intended behaviour? If so, how do we stop needless validations of inputs the user hasn't touched?

• validation
• primevue

1 Answer 1

A similar problem as this one has been reported and accepted as a bug:

https://github/primefaces/primevue/issues/7416