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

[whatwg] Scoped tabindex proposal

From: Ric Hardacre <whatwg@cycloid.f9.co.uk>
Date: Fri, 01 Sep 2006 12:12:22 +0100
Message-ID: <44F81596.50301@cycloid.f9.co.uk>


Andrew Fedoniouk wrote:
> 
> It is better to use another attribute for that, say - tabgroup.
> It should accept exactly the same set of values as tabindex.
> 
> <input tabindex="1" />
> <foo tabgroup="2">
>    <input tabindex="1" />
>    <input tabindex="2" />
> </foo>
> <input tabindex="3" />
> 
> The order of tab traversal of inputs will be in this case as
> their natural order (in this case).
> 
> tabgroup marked element may or may not have tabindex
> defined - so it can be focusable by itself.
> If both tabgroup and tabindex are defined and have numeric values then
> tabindex value is used as an index.
> 
> So it will be possible to say:
> <foo tabindex="2" tabgroup >
> 
> Andrew Fedoniouk.
> http://terrainformatica.com
> 
> 

how about allowing decimals, where by default "1" implies "1.0"? :

 <input tabindex="1" />
 <foo tabindex="2">
    <input tabindex="2.1" />
    <input tabindex="2.2" />
 </foo>
 <input tabindex="3" />

This also allows you to quickly associate the grouping of an input by
it's value when viewing the source:

<table>
<tr>
   <td><input tabindex="1.1" /></td>
   <td><input tabindex="2.1" /></td>
</tr>
<tr>
   <td><input tabindex="1.2" /></td>
   <td><input tabindex="2.2" /></td>
</tr>
<tr>
   <td></td>
   <td><button tabindex="3" /></td>
</tr>
</table>

obviously the above example could have just used tabindex 1 through 5
but you get the point

Ric Hardacre
http://www.cyclomedia.co.uk/
Received on Friday, 1 September 2006 04:12:22 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:29 UTC