[Bug 10909] Clarify how fieldset's first legend should behave if the fieldset is disabled because of another disabled fieldset

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10909

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

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

--- Comment #4 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-10-14 07:40:16 UTC ---
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: see diff given below
Rationale: The spec actually is pretty clear. It says that disabled will
disable certain controls. Nothing says that the lack of the disabled attribute
enables anything; indeed, there are many cases where that isn't the case (the
simplest being the control itself being independently disabled).

I've added an example though that shows this case.

-- 
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, 14 October 2010 07:40:18 UTC