-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve description of readonly
attribute
#9496
Comments
I agree that this is somewhat confusing, but I think the current text is still accurate. |
Thanks. You definitely hit the nail on the head as to why I was confused by this:
I don't know if the docs are getting that across right now. I still think this line may be incorrect, because it seems to mistake cause for effect:
I don't think it's true that
|
readonly
attribute (or mutability)readonly
attribute
I don't think this is accurate. See mdn/content#29140 for an example. |
The pseudo-class matches all elements that do not match |
"The pseudo-class matches all elements that do not match Yes, that is my point, |
I'm not sure what you are suggesting. |
The description of the
readonly
attribute (or the definition of mutability) is currently inaccurate.The spec clearly states that the
readonly
attribute makes a form control immutable:And that mutability is whether or not the user can modify value or checkedness:
But when a radio button or checkbox control is
readonly
, the user can still modify checkedness. So I think one of these definitions needs to be updated.I also think this note could be made clearer:
I think it would be better to state that the
readonly
attribute is only useful on text controls because it does not prevents the user from modifying checkedness of a radio button or checkbox control, which means a user can still change its submitted value by changing its checkedness. The note as currently written never quite makes it to this point of clarity.The text was updated successfully, but these errors were encountered: