10372 2010-08-15 15:51:06 +0000 Authors should ensure that in each set of radio buttons that one is initially "on". Because some have made bad UI choices you should not recant this rule! At all times, exactly one of the radio buttons in a set is checked. Radio button Only one item 2010-10-04 13:56:12 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#radio-button-state P3 normal --- 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 37429 0 contributor 2010-08-15 15:51:06 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#radio-button-state Comment: Authors should ensure that in each set of radio buttons that one is initially "on". Because some have made bad UI choices you should not recant this rule! At all times, exactly one of the radio buttons in a set is checked. Radio button Only one item in a group can be selected. The Radio name comes from the mechanical push-button group on a car radio receiver. Selecting a new item from the group's buttons also deselects the previously selected button. Only the selected choice should be accessible using the Tab key. The Radio control should be used to choose "one" option from a set of mutually exclusive choices "at all times". I beg you not to back set on good UI because other do not know better! Andrew Arnone andrew.arnone@hartfordlife.com Posted from: 71.234.122.23 39242 1 ian 2010-09-24 01:23:56 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: If I'm not mistaken, we used to have this in the spec. Unfortunately, it's so common to make this mistake that many people don't agree it's a mistake. I don't want to fight this fight. I encourage you to escalate this issue by adding the TrackerRequest keyword to it; if there are others that agree that it we should enforce good UI here, it still has a chance to be changed.