W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2011

[Bug 11794] We should handle the case of a bunch of required controls all being hidden at once — the author shouldn't have to also go in an remove the 'required' attribute on each one. Maybe make hidden="" bar things from constraint validation?

From: <bugzilla@jessica.w3.org>
Date: Wed, 16 Feb 2011 08:15:26 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PpcXm-0004DH-Pd@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11794

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |LATER

--- Comment #10 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-02-16 08:15:26 UTC ---
The use case in question is something like a list where each list item can be
toggled between representing either nothing or a set of further fields nested
within it. You want each nested field to be disabled when the parent list item
is in the "off" state, and enabled otherwise, and you don't want to have to
crawl the tree manually each time.

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: Partially Accepted
Change Description: none yet
Rationale: I'm going to postpone this for now, since there are temporary (if
awkward) workarounds in the use of <fieldset> or in the use of utility
functions that crawl the tree marking elements as disabled, and since the use
case isn't a huge use case, and since the proposed solutions have real problems
and I don't have a better proposal at the moment.

-- 
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 Wednesday, 16 February 2011 08:15:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 16 February 2011 08:15:40 GMT