W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2010

[Bug 10833] The element should only suffer from being missing if all of the checkbox choices are unselected - like radio buttons

From: <bugzilla@jessica.w3.org>
Date: Thu, 07 Oct 2010 22:05:21 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P3yaX-00068Z-Fq@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10833

--- Comment #3 from Maciej Stachowiak <mjs@apple.com> 2010-10-07 22:05:20 UTC ---
I don't see a problem with implementing either behavior.

However, checkboxes, unlike radio buttons, do not have any behavior currently
that groups via name. This change would be the first to introduce it. Certainly
it would not make sense to apply to unnamed checkboxes or to all checkboxes in
a form. For example, often a EULA form will have separate "I have read this"
and "I agree" checkboxes in the same form which are both independently required
to be checked. So this would be the first behavior to treat checkboxes as
grouped like radio buttons, which might be confusing.

"Required" also seems like an odd concept for a single checkbox. There are
cases (like the aforementioned EULA) where checking a particular checkbox is
mandatory to submit the form. But in other cases, on and off are both equally
valid states, and can be a willful choice by the user. So that seems different
from other uses of required, where they form control fails validation only if,
in some sense, "nothing has been chosen".

-- 
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 Thursday, 7 October 2010 22:05:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:31 UTC