Hi,
From: Martin Atkins <[EMAIL PROTECTED]>
The table might not be focusable, but it needs to be in the tab order in
some sense in order to resolve that local tabindex="1" into a global
tabindex.
For example:
<a id="outside1" href="..." tabindex="1">...</a>
<div tabindex="scoped" id="container1">
<a id="inside1" href="..." tabindex="1">...</a>
</div>
<div tabindex="scoped" id="container2">
<a id="inside2" href="..." tabindex="1">...</a>
</div>
<a id="outside2" href="..." tabindex="2">...</a>
What is the global tab order now?
I could see arguments for either:
#outside1
#inside1
#inside2
#outside2
(DOM order)
or...
#outside1
#outside2
#inside1
#inside2
(all of the explicit tabindexes first in index order, followed by
everything else in DOM order)
The second one is what I had in mind.
Now what if I want the elements of #container2 to be before those of
#container1 in the tab order? Can I also give these DIVs a tabindex?
Then it would be better to drop the tabindex="scoped" idea and instead
define that any tabindex element is a scoping element, so you would use
tabindex="1" on #container2 and tabindex="2" on #container1. I think this
makes more sense than changing tabIndex to a DOMString, and it is more
flexible.
Regards,
Simon Pieters
