11212 2010-11-04 00:21:36 +0000 Make all the radio button group suffering from being missing (instead of only radio's with the required attribute) 2011-08-04 05:16:24 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED FIXED P2 normal --- 1 mounir ian annevk ayg douglas.wright ian jonas mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 42095 0 mounir 2010-11-04 00:21:36 +0000 Currently, when a radio button is required, it will suffer from being missing if no radio elements in the radio button group is checked. However, radio elements in the group will not suffer from being missing if they do not have the required attribute. In other words, if you try to style invalid elements with :invalid, and do: <input type='radio' name='s' value='M' required> <input type='radio' name='s' value='F'> only the first element will be styled. I think we should move the requirement to the radio button group that way: "The radio button group suffers from being missing if one of the input elements in the radio button group is required and all of them have a checkedness that is false." and radio elements would have this constraint: "If the radio button group is suffering from being missing, the element is suffering from being missing.". That way, all radio elements in the same radio button group will have the same validity state. That would be less annoying for authors and error proof while making things clearer (IMO). 42112 1 douglas.wright 2010-11-04 10:08:25 +0000 See related bug 10833. 42114 2 douglas.wright 2010-11-04 10:18:52 +0000 (In reply to comment #1) > See related bug 10833. Ignore me 45335 3 ian 2011-02-10 02:19:30 +0000 I replied to this last month, here: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-January/029733.html I will reply to its only reply so far in due course, and then update this bug accordingly: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-January/029808.html 45341 4 mounir 2011-02-10 09:20:06 +0000 FWIW, it's implemented in current Firefox betas. 46378 5 ian 2011-03-04 23:42:34 +0000 Opera does what the spec says; Firefox does what this proposal says. Are there any other implementations of required="" on radio buttons? http://software.hixie.ch/utilities/js/live-dom-viewer/saved/864 46431 6 mounir 2011-03-06 13:09:46 +0000 Anne, I think you agreed with this change when I sent an email to the mailing list. Do Opera has plan to update its implementation? 46432 7 annevk 2011-03-06 14:00:40 +0000 No immediate plans, but we are definitely cool with changing our behavior for the better in due course. That's even easier if the specification requires it to be different and there's testcases effectively "blaming" us for being too fast with implementing this stuff :-) 48148 8 ian 2011-05-06 00:38:19 +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: Accepted Change Description: see diff given below Rationale: see discussion above. 48149 9 contributor 2011-05-06 00:38:34 +0000 Checked in as WHATWG revision r6094. Check-in comment: Make it so that if you make one <input type=radio> required, they all end up required. http://html5.org/tools/web-apps-tracker?from=6093&to=6094 53693 10 mike 2011-08-04 05:16:24 +0000 mass-move component to LC1