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
The Checkbox control is hardcoded to always setreadOnly on its Input, even if you don't pass the readOnly prop.
This means the element is always in the readonly state, which causes HTML validation to always pass, even if the element is actually in an invalid state (e.g. being required).
Expected Result
It should be possible to use required with a Checkbox component and have form validation and methods such as checkValidity() work correctly.
Actual Result
Expected form validation does not occur because the element is in the readonly state. This allows a user to submit a form without checking a required value, even when you've set the required prop.
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you've completed all the fields in the issue template so we can best help.
We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
Bug Report
Steps
The Checkbox control is hardcoded to always set
readOnly
on its Input, even if you don't pass thereadOnly
prop.This means the element is always in the readonly state, which causes HTML validation to always pass, even if the element is actually in an invalid state (e.g. being
required
).Expected Result
It should be possible to use
required
with a Checkbox component and have form validation and methods such ascheckValidity()
work correctly.Actual Result
Expected form validation does not occur because the element is in the readonly state. This allows a user to submit a form without checking a required value, even when you've set the
required
prop.Version
2.1.3
Testcase
https://codesandbox.io/s/semantic-ui-react-checkbox-is-always-readonly-oyeow5
The text was updated successfully, but these errors were encountered: