- From: <bugzilla@jessica.w3.org>
- Date: Tue, 13 May 2014 16:34:04 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25614 --- Comment #9 from James Craig <jcraig@apple.com> --- (In reply to steve faulkner from comment #6) > (In reply to James Craig from comment #4) > > > Also... > > > > Since the @disabled boolean attribute has been available longer, do you have > > any objection to including these two in the Strong table? > > > > ''' > > input, select, or textarea element with a disabled attribute. > > The aria-disabled state set to "true". > > If specified, the aria-disabled state must be set to "true"' > > > > input, select, or textarea element without a disabled attribute. > > The aria-disabled state set to "false". > > If specified, the aria-disabled state must be set to "false" > > ''' > > can do if you think it makes what is already there clearer Are you talking about this one row or is there something more I missed? > Element that is disabled. The aria-disabled state set to "true". Yes, I think it's more clear because it would allow validation errors on examples like this: <input aria-disabled="true"> (missing @disabled). Seems like you could also use this format if you preferred. """ Element that is disabled. The aria-disabled state set to "true". If specified, the aria-disabled state must be set to "true". Element that is not disabled. The aria-disabled state set to "false". If specified, the aria-disabled state must be set to "false". """ -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 13 May 2014 16:34:06 UTC