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
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://forum.primefaces.org/viewforum.php?f=57
Current behavior
I have this error, however I've passed the readOnly prop into the Checkbox component: Warning: Failed prop type: You provided a `checked` prop to a form field without an `onChange` handler. This will render a read-only field. If the field should be mutable use `defaultChecked`. Otherwise, set either `onChange` or `readOnly`.
Another error I'm experiencing is: Warning: Failed prop type: The prop `onChange` is marked as required in `Checkbox`, but its value is `null`.
The existence of the onChange prop is checked here so no need to mark onChange prop as required in order to be able the make readonly checkboxes.
Expected behavior
Be able to make readonly checkboxes.
React version:
16.3
PrimeReact version:
1.5.1
Browser: all
Language: ES6/7
The text was updated successfully, but these errors were encountered:
I'm submitting a ... (check one with "x")
Current behavior
I have this error, however I've passed the
readOnly
prop into the Checkbox component:Warning: Failed prop type: You provided a `checked` prop to a form field without an `onChange` handler. This will render a read-only field. If the field should be mutable use `defaultChecked`. Otherwise, set either `onChange` or `readOnly`.
Another error I'm experiencing is:
Warning: Failed prop type: The prop `onChange` is marked as required in `Checkbox`, but its value is `null`.
The existence of the onChange prop is checked here so no need to mark
onChange
prop as required in order to be able the make readonly checkboxes.Expected behavior
Be able to make readonly checkboxes.
React version:
16.3
PrimeReact version:
1.5.1
Browser: all
Language: ES6/7
The text was updated successfully, but these errors were encountered: