[whatwg] fieldset disabled and first legend
mounir.lamouri at gmail.com
Fri Sep 24 13:57:38 PDT 2010
On 09/21/2010 01:06 AM, Jonas Sicking wrote:
>> This is very interesting to have the elements inside the first legend to
>> not be disabled. I guess the idea is to have a checkbox enabling some
>> options. For example, "advanced options" in a configuration.
>> However, the specification seems to miss one edge case. What if a
>> fieldset has been disabled because it is inside a disabled fieldset?
>> Depending on how you read the current specification, you can consider
>> that the elements inside the first legend of the second fieldset should
>> be disabled or not. My opinion is, those elements should be disabled and
>> that's the current Gecko's behavior (current nightly and next beta).
>> It would be good to add something mentioning this edge case.
> This is arguably already defined. Consider the case of:
> <fieldset disabled>
> <legend><input type=checkbox></legend>
> In this case the <input> is inside the *outer* fieldset, but not
> inside *its* first <legend> (since it doesn't have one). Thus it
> should be disabled.
This is what I meant by "Depending on how you read the current
specification, you can consider that the elements inside the first
legend of the second fieldset should be disabled or not".
If that was Hixie's intention, I think adding a non-normative paragraph
explaining the edge case would be nice. Otherwise, making the
specification more clear would be required.
More information about the whatwg