You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Observe that the Submit button correctly changes state from disabled to enabled
Type a second character into the input field
Observe that the Submit button erroneously changes state from enabled to disabled despite the fact that the form is valid
Look at the console logs which show that isValidating is stuck in true state, which is causing the submit button to be disabled
Change the version of react-hook-form to 7.39.7 in package.json and observe that isValidating does not get stuck in true state after typing more than one character into the input field
If you change the form's mode from onChange to onBlur, you can type multiple characters into the field initially, but as soon as the field is blurred isValidating gets stuck in true state.
Expected behaviour
The isValidating property should update from true to false once validation has completed. This issue seems similar to #9251, but in this case the behavior can be reproduced consistently, and it's just using vanilla yum validation. This behavior was introduced in 7.40.0. It works as expected in 7.39.7 and prior.
Version Number
7.40.0
Codesandbox/Expo snack
https://codesandbox.io/s/react-hook-form-isvalidating-stuck-js9gpj?file=/src/index.tsx
Steps to reproduce
isValidating
is stuck intrue
state, which is causing the submit button to be disabledreact-hook-form
to 7.39.7 inpackage.json
and observe thatisValidating
does not get stuck intrue
state after typing more than one character into the input fieldIf you change the form's
mode
fromonChange
toonBlur
, you can type multiple characters into the field initially, but as soon as the field is blurredisValidating
gets stuck intrue
state.Expected behaviour
The
isValidating
property should update fromtrue
tofalse
once validation has completed. This issue seems similar to #9251, but in this case the behavior can be reproduced consistently, and it's just using vanilla yum validation. This behavior was introduced in 7.40.0. It works as expected in 7.39.7 and prior.What browsers are you seeing the problem on?
Chrome
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: