Search and Top Navigation
#5644 closed bug (wontfix)
Opened May 22, 2010 09:44AM UTC
Closed October 15, 2012 04:18PM UTC
Last modified August 30, 2013 06:40PM UTC
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.
Attachments (0)
Change History (5)
Changed February 27, 2012 01:43PM UTC by comment:1
Changed October 11, 2012 09:04PM UTC by comment:2
milestone: | TBD → 1.11.0 |
---|
Changed October 15, 2012 04:18PM UTC by comment:3
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.
Changed August 29, 2013 02:33AM UTC by comment:4
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.
Changed August 30, 2013 06:40PM UTC by comment:5
So to clarify: the request is to treat readonly the same as disabled in terms of user perception and interaction?
Do we want to support this? Is there a difference between readonly and disabled for radio buttons?