- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 27 Feb 2010 02:27:18 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9160
Summary: Constraint validation ought to match a radio group; that
is, if any checkbox in the group is checked, the whole
control is valid. Not only would this change make the
API consistent for mutually-exclusive (radio) and
mutually-inexclusive (checkbox) widget
Product: HTML WG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-
work/#checkbox-state
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: HTML5 spec bugs
AssignedTo: dave.null@w3.org
ReportedBy: contributor@whatwg.org
QAContact: public-html-bugzilla@w3.org
CC: ian@hixie.ch, mike@w3.org, public-html@w3.org
Section: http://www.whatwg.org/specs/web-apps/current-work/#checkbox-state
Comment:
Constraint validation ought to match a radio group; that is, if any checkbox
in the group is checked, the whole control is valid. Not only would this
change make the API consistent for mutually-exclusive (radio) and
mutually-inexclusive (checkbox) widgets, but it has a broader set of
applications. It is the rare case that someone would want to force a box to
be checked with the validation API, but enforcing that at least one box in a
group is checked is the exact sort of application that this API was designed
for. If someone wants to force a box to be checked, he can always put it in
its own group.
Posted from: 75.141.192.2
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Saturday, 27 February 2010 02:27:20 UTC