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

[Bug 9817] Details element Focus problem

From: <bugzilla@jessica.w3.org>
Date: Fri, 10 Sep 2010 05:37:46 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1OtwJ0-0002KX-8a@jessica.w3.org>

--- Comment #6 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>  2010-09-10 05:37:45 ---
(In reply to comment #5)
> (In reply to comment #2)
> > I recommend only details receive focus and that the summary be a label for it.
> > In other words <summary> should not support tabindex
> Was this something you said based on how <label> works in Webkit? 
> In Webkit, then it isn't possible to jump to the <label> via tabbing, no matter
> if you set the @tabindex attribute for <label>. As one tabs, the <label> is
> simply jumped over, in favour of the next element on the index list.

Webkit also doesn't allow focus on <legend> - only on <fieldset>.

Regarding your expensive-for-AT-to-implement argument: Isn't the
fieldset/legend/label/input combo quite complex as well? Do you simply want to
avoid the same kind of complexitiy?

It seems like giving focus to the <summary> element, is quite logical to
authors. See this early <details> demo: 
(article: http://mathiasbynens.be/notes/html5-details-jquery) 

In my view we have a similar dilema for <table>: I always found it illogical
that @summary was located at <table> instad of on <caption> - as if one coudn't
decide if the caption or the container should carry the caption role.

Also see bug 10483: When we have captions, then I think it is important that
that there is strong link between the captioning elemenet and the container
element, as that element represents the entire element. E.g. if I had a page
full of table elements, then the natural thing - if I were to jump from table
to table - would be to jump from caption to caption. Should I want to copy the
entire table, then it is just to move one parent up. And if I want to focus on
the content, then I visit the adjacent element of the caption. The captioning
element is like the semantic tag of the framing element  -

Finally, it seems like you consider the focus-ability closely linked to the
role.  In that regard, how do you evaluate that <summary> at the moment has
strong native semantics role="heading"?

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 Friday, 10 September 2010 05:37:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:24 UTC