W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2012

[whatwg] tabindexscope

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 31 Jan 2012 01:18:43 +0000 (UTC)
Message-ID: <Pine.LNX.4.64.1201310118220.18697@ps20323.dreamhostps.com>
On Mon, 30 Jan 2012, Erik Arvidsson wrote:
> On Mon, Jan 30, 2012 at 13:54, Ian Hickson <ian at hixie.ch> wrote:
> > Surely that would be better than having authors manage local regions 
> > for tabindex, especially since the positioning depends on the CSS 
> > level, not the HTML level, and thus trying to manage the tabindex in 
> > the HTML would be a layering violation anyway.
> 
> Assume the developer is building a component/widget/group of elements in 
> isolation from the rest of the application/page. He wants to define the 
> tab order of the elements under his control to be something else than 
> the browser provided default order. To do this correctly today the 
> developer would have to update tabindex on all existing keyboard 
> focusable elements.
> 
> What you are saying is that the developer should not try to manage the 
> tabindex which to me implies that user agents should ultimately ignore 
> the developer provided tabindex?

For components, we should do what we did with XBL2 -- say that within a 
component, tabindex="" values are scoped to the component.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 30 January 2012 17:18:43 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:10 UTC