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

RE: Fieldset disabled attribute and descendants

From: Adrian Bateman <adrianba@microsoft.com>
Date: Mon, 18 Jan 2010 17:56:28 +0000
To: Ian Hickson <ian@hixie.ch>
CC: HTMLWG WG <public-html@w3.org>
Message-ID: <104E6B5B6535E849970CDFBB1C5216EB1D08880F@TK5EX14MBXC140.redmond.corp.microsoft.com>
On Wednesday, January 13, 2010 2:32 PM, Ian Hickson wrote:
> On Wed, 13 Jan 2010, Adrian Bateman wrote:
> >
> > http://dev.w3.org/html5/spec/Overview.html#the-fieldset-element
> >
> > In the description for the <fieldset> disabled attribute, the spec
> says:
> >
> > "The disabled attribute, when specified, causes all the form control
> > descendants of the fieldset element, excluding those that are
> > descendants of the fieldset element's first legend element child, if
> > any, to be disabled."
> >
> > Is there a reason why the disabled attribute shouldn't also disable
> > controls that are descendants of the first legend element?
> 
> Generally speaking, the main use case for this is a checkbox in the
> legend used to enable or disable the entire fieldset.
> 
> For example:
> 
>  +-- [ ] Shipping address is different from billing address --------+
>  |                                                                  |
>  | (form fields for shipping address)                               |
>  |                                                                  |
>  +------------------------------------------------------------------+

Thanks Ian (and Philip who suggested the same use case). I think it would be good to include this as an informative example in the spec. We've filed a bug on this behaviour for IE but given the lack of interop on this feature across browsers it might not be a high priority for us.

Cheers,

Adrian.
Received on Monday, 18 January 2010 17:57:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:58 GMT