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 21051 - "Enabling and disabling of form controls" allows disabling a parent element to disable that element's contents if and only if that element is a fieldset. However, the ability to do such group disablin [...]
Summary: "Enabling and disabling of form controls" allows disabling a parent element t...
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-19 20:04 UTC by contributor
Modified: 2013-03-25 23:53 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2013-02-19 20:04:23 UTC 
Specification: http://www.w3.org/TR/2011/WD-html5-20110525/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top

Comment:
"Enabling and disabling of form controls" allows disabling a parent element to
disable that element's contents if and only if that element is a fieldset.
However, the ability to do such group disabling is useful for other elements,
and the ARIA spec "correctly" defines the aria-disabled behavior as applying
to all child elements of the disabled container.

Scenario: A tab control which wishes to disable an entire tab of unknown
content, without interfering with the content directly. Applying "disabled" to
the tabpanel element itself would allow declarative disabling of regions
without non-semantic use of fieldset elements.

Posted from: 2001:4898:90:1004:1420:3dad:494b:4625
User agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0)
Comment 1 Ian 'Hixie' Hickson 2013-03-25 23:53:56 UTC 
Just use <fieldset> as the tab panel. That's exactly the right semantic — a group of controls.