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

[whatwg] tabindexscope

From: Erik Arvidsson <arv@chromium.org>
Date: Mon, 30 Jan 2012 16:58:38 -0800
Message-ID: <CAJ8+GojbzUWjOWUgn2dk5_NqNXuTwg=-KyRqYMwqGr37pMVmew@mail.gmail.com>
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?

Received on Monday, 30 January 2012 16:58:38 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:39 UTC