[whatwg] Scoped tabindex proposal

• From: Martin Atkins <mart@degeneration.co.uk>
• Date: Thu, 31 Aug 2006 22:26:43 +0100
• Message-ID: <44F75413.2050406@degeneration.co.uk>

Simon Pieters wrote:
> 
> 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.
> 

And, I guess, tabindex="0" would be roughly equivalent to your 
tabindex="scoped".

Seems reasonable to me.

Received on Thursday, 31 August 2006 14:26:43 UTC