Bug 19693
| Summary: | Deselecting a radio button not possible | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Rüdiger Cordes <rc> |
| Component: | Evangelism | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | webkit |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Rüdiger Cordes
When filling out a form and clicking on a radio button by mistake the possibility of deselecting it would be nice.
Its not a big bug but I think it would be nice. FileMaker for example has this feature with shift click.
Why not implementing it in webkit?
;-)
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Robert Blaut
I isn't possible according HTML 4.01 recommendation:
"Radio buttons are like checkboxes except that when several share the same control name, they are mutually exclusive: when one is switched "on", all others with the same name are switched "off". The INPUT element is used to create a radio button control.
If no radio button in a set sharing the same control name is initially "on", user agent behavior for choosing which control is initially "on" is undefined. Note. Since existing implementations handle this case differently, the current specification differs from RFC 1866 ([RFC1866] section 8.1.2.4), which states:
At all times, exactly one of the radio buttons in a set is checked. If none of the <INPUT> elements of a set of radio buttons specifies `CHECKED', then the user agent must check the first radio button of the set initially.
Since user agent behavior differs, authors should ensure that in each set of radio buttons that one is initially "on"." [http://www.w3.org/TR/REC-html40/interact/forms.html#radio]
So this report isn't possible to be proceeded.
Rüdiger Cordes
Thanks for your investigation.
This means all times is an additional radio button necessary for deselecting/selecting other.
It consumes space on the website while reducing clearness.
Checkboxes ask only about a potential attribute. When radio buttons are like checkboxes only with the additional feature that selection of one of them deselects the others then this statement is in contrast with the demand of presenting all possible choices.
Yes, I see the problem. To get a good quality of data it may be good to show all options but nevertheless the user can forget to click on a radio button. Left is the reason to have only one and ergonomic guideline for the radio buttons but this collides with the reality.
When asking for blood groups and only A or B are important why shall the user click on others?
Additional work for him with no benefit. I have a form with 4,000 radio buttons. When I can avoid the 'other'-button it reduces them to 3000. This is nicer and faster.
Yes, I know we are discussing here things others should do on another platform ;-) Just to collect here all arguments for a deselect functionality ;-) Rüdiger