18058 2012-07-18 16:18:26 +0000 Please provide example for required attribute with radiobutton group. Since that differs from other implementations. 2013-07-03 07:15:15 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#the-required-attribute CR P3 normal --- 1 contributor faulkner.steve faulkner.steve ian mike public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 70584 0 contributor 2012-07-18 16:18:26 +0000 This was was cloned from bug 16029 as part of operation convergence. Originally filed: 2012-02-19 15:42:00 +0000 ================================================================================ #0 contributor@whatwg.org 2012-02-19 15:42:03 +0000 -------------------------------------------------------------------------------- Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html Multipage: http://www.whatwg.org/C#the-required-attribute Complete: http://www.whatwg.org/c#the-required-attribute Comment: Please provide example for required attribute with radiobutton group. Since that differs from other implementations. Posted from: 88.241.251.7 User agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 ================================================================================ #1 Michael Cooper 2012-02-21 17:06:51 +0000 -------------------------------------------------------------------------------- HTML Accessibility Task Force bug triage sub-team created bug 16061 that blocks this. This bug requests an example of required radio button groups. 16061 requests the feature to enable that, via @required on fieldset. Once that feature is created, the block this bug can be removed and hopefully the example created. ================================================================================ 85653 1 faulkner.steve 2013-04-06 15:01:43 +0000 kinking this one over to hixie, appears the original bug was resolved wontfix but does not appear to be any reason. From testing in firefox it appears that if one input[radio] in a radio group has a required all the inputs[radio] in the group become required, which does seem like the correct behaviour. Cannot find anywhere where this is specified, if I am not missing anything appears like an omission. 86169 2 faulkner.steve 2013-04-14 07:32:01 +0000 works for hixie, but I consider the reporters request to add an example is reasonable and useful as it improves understanding for authors. so I will add an example to the HTML spec 90040 3 faulkner.steve 2013-06-30 10:52:41 +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: added example of use of required attribute one radio button in a group https://github.com/w3c/html/commit/6a04ea28f0988bc0247990c134460a0751378dbf Rationale: agreed that it it would help to provide an example Since it differs from other implementations. 90068 4 ian 2013-07-01 17:00:42 +0000 For the record, it was marked WORKSFORME because there's already such examples in the spec. Adding redundant examples just makes the spec longer and harder to read (since readers try to figure out what's special about the redundant examples). 90080 5 faulkner.steve 2013-07-01 19:51:00 +0000 (In reply to comment #4) > For the record, it was marked WORKSFORME because there's already such > examples in the spec. Adding redundant examples just makes the spec longer > and harder to read (since readers try to figure out what's special about the > redundant examples). If you are claiming the example is redundant, why not provide a pointer to the example that the one added duplicates? 90082 6 ian 2013-07-01 19:57:17 +0000 There's one in the "Client-side form validation" section, for instance. The first place that talks about required="". 90086 7 faulkner.steve 2013-07-01 21:31:33 +0000 (In reply to comment #6) > There's one in the "Client-side form validation" section, for instance. The > first place that talks about required="". Oh it thought you meant there was an example of what the commenter was asking for, which that example does not provide. I saw that example when i checked originally but as it clearly dos not what the added example shows, there is no redundancy. 90200 8 ian 2013-07-03 00:04:14 +0000 "Please provide example for required attribute with radiobutton group. Since that differs from other implementations." The example in question does exactly that? What am I missing? The only thing your example does that's different is that it has the confusing markup where you only include the required="" attribute on one of the controls, but that's bad style that shouldn't be encouraged. 90215 9 faulkner.steve 2013-07-03 07:15:15 +0000 (In reply to comment #8) > but that's bad style that shouldn't be encouraged missed your proclamation that adding redundant attributes is good practice