#5644 closed bug (wontfix)
Button: Buttonset radio buttons ignore readonly attribute
Reported by: | felixg | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 1.11.0 |
Component: | ui.button | Version: | 1.8 |
Keywords: | readonly | Cc: | |
Blocked by: | Blocking: |
Description
When creating a buttonset of <input type="radio" .../> the readonly attribute is ignored, and the user can change the button's state.
Change History (5)
comment:1 Changed 11 years ago by
comment:2 Changed 10 years ago by
Milestone: | TBD → 1.11.0 |
---|
comment:3 Changed 10 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Summary: | Buttonset radio buttons ignore readonly attribute → Button: Buttonset radio buttons ignore readonly attribute |
The browsers do not prevent users from changing to a non-readonly option in the group if a single item is marked readonly or disabled. Logically, the entire group should be disabled if you want to prevent a user from changing the state.
comment:4 Changed 9 years ago by
if an input is disabled, its value won't be included when the form is submitted. While it's readonly, the value will be submitted. It affects the back-end processing.
comment:5 Changed 9 years ago by
So to clarify: the request is to treat readonly the same as disabled in terms of user perception and interaction?
Note: See
TracTickets for help on using
tickets.
Do we want to support this? Is there a difference between readonly and disabled for radio buttons?