W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2006

[whatwg] Scoped tabindex proposal

From: Simon Pieters <zcorpan@hotmail.com>
Date: Sat, 02 Sep 2006 16:17:47 +0000
Message-ID: <BAY109-F156EDC848DE0D0E398C227B43D0@phx.gbl>

From: Aaron Leventhal <aaronlev@moonset.net>
>tabindex="-1" doesn't just remove items from the tab order. It also makes 
>items focusable via mouse click or script, which is important when 
>designing custom container widgets like spreadsheets, etc. via Javascript. 
>In fact any negative value does it.


>Don't try to overload the tabindex attribute.

tabindex="scoped" is overloading indeed, but changing the tab order 
algorithm isn't really overloading the tabindex attribute (if we would say 
that all tabindex elements are scoping elements).

>First, the browsers currently optimize it knowing that it's an integer.

I agree that tabindex should still be a long (and not DOMString).

>Second, the scoping is orthogonal.

Then it would be better to have a separate attribute. That also allows the 
use of the current tab order for nested tabindex elements, and the ability 
to declare unfocusable scoping elements.

>Third, magic values are less readable. It's voodoo.


Simon Pieters
Received on Saturday, 2 September 2006 09:17:47 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:48 UTC