This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13323 - In section 4.10.21 "Constraints" (under "Association of controls and forms"), the definition for "Suffering from being missing" includes the text "... or, in the case of an element in a radio button group, any of the other elements in the group has a requ
Summary: In section 4.10.21 "Constraints" (under "Association of controls and forms"),...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-21 20:02 UTC by contributor
Modified: 2011-08-10 20:45 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2011-07-21 20:02:59 UTC 
Specification: http://dev.w3.org/html5/spec/Overview.html
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
In section 4.10.21 "Constraints" (under "Association of controls and forms"),
the definition for "Suffering from being missing" includes the text "... or,
in the case of an element in a radio button group, any of the other elements
in the group has a required attribute".  I think this should also apply to
checkbox elements in the same group.  In other words, if any of the checkbox
elements with a given name have the "required" attribute, then at least one of
the checkboxes should be selected (not necessarily the checkbox with the
"required" attribute).	I can see arguments for the opposite behavior, but the
reality is that it is more useful to require at least one checkbox to be
checked than to require a specific checkbox (and if you require a specific
checkbox then it is usually in its own group by itself, and therefore it would
behave as intended).  In my opinion, it is counterintuitive to make the
checkbox behavior different than the radio button behavior in this case.

Posted from: 169.237.132.160
User agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110420 Firefox/3.6.17
Comment 1 Michael[tm] Smith 2011-08-04 05:02:46 UTC 
mass-moved component to LC1
Comment 2 Ian 'Hixie' Hickson 2011-08-10 20:45:52 UTC 
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: 

As far as I am aware, nothing links checkboxes together currently — there's no more of a relationship between two type=checkbox inputs with the same name and two type=text inputs with the same name. type=radio are a special case of their own.

We could change that for type=checkbox and required="", but I'm skeptical that it's that good an idea. If you really want the user to select one or more from a list, use <select multiple required>.