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
Hi ^^. I wonder why fields in disabled fieldsets are still validated, though individually disabled fields are (thankfully) not. Is there just no way for the library to know if a field has a disabled ancestor or is this behavior intentional?
I know there are ways to work around this and manually disable/unregister the fields, but I think it would be really nice and much easier if I a disabled fieldset would simply disable the validation for its descendants. Just like with the native HTML5 from validation.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
React Hook Form
-
Hi ^^. I wonder why fields in disabled fieldsets are still validated, though individually disabled fields are (thankfully) not. Is there just no way for the library to know if a field has a disabled ancestor or is this behavior intentional?
I know there are ways to work around this and manually disable/unregister the fields, but I think it would be really nice and much easier if I a disabled fieldset would simply disable the validation for its descendants. Just like with the native HTML5 from validation.
Beta Was this translation helpful? Give feedback.
All reactions