[Bug 10066] replace section 3.2.6 with the alternative spec text provided

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





--- Comment #16 from steve faulkner <faulkner.steve@gmail.com>  2010-08-22 14:52:07 ---
Hi Maciej, 

you wrote:
> That doesn't seem quite right to me. <details> is intended to be presented much

note that we are also unsure about this
in the revised spec text table under details it states:

"details element * may change based on resolution of bug 9817"
[http://www.w3.org/Bugs/Public/show_bug.cgi?id=9817]

Note: default mappings indicated in the table are not meant to be advice for
implementors.



(In reply to comment #15)
> Thanks, Steve, your comments here are very helpful. I believe the bug should be
> ready for action by the editor now. I have comments on just one of these:
> (In reply to comment #14)
> > 
> > 
> > > details - changed from no role to "button" role
> > 
> > from reading the spec we concluded that details may have a default role of
> > button as it is likely to be the element a user will interact with to show/hide
> > the details content.
> That doesn't seem quite right to me. <details> is intended to be presented much
> like a "disclosure triangle" control on Mac OS X, it includes an affordance
> indicating the presence of details, the label inside the <summary> element, and
> the actual details content. I don't think this acts like a button - most of it
> (the details part) will not even react to clicks. I don't think there is an
> appropriate ARIA role for this whole element, although it could be presented
> via assistive technologies as a compound control which among other things
> includes a button.

-- 
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 Sunday, 22 August 2010 14:52:10 UTC