W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2011

[whatwg] Proposal: tabindexscope

From: Eric Sh. <shedokan1@gmail.com>
Date: Tue, 8 Nov 2011 23:52:45 +0200
Message-ID: <CAMTXT=9i2znakic2XeGCXWaYjWegxGYt+wasVSrjuS=b95J6+Q@mail.gmail.com>
On Tue, Nov 8, 2011 at 11:44 PM, Ojan Vafai <ojan at chromium.org> wrote:

> On Tue, Nov 8, 2011 at 1:39 PM, Eric Sh. <shedokan1 at gmail.com> wrote:
>
>> I don't understand where are you going with this, is it a proposal for a
>> tab index scope?
>>
>
> Yes.
>

Then I think it's a good idea, in modern web applications using tab(for
example in gmail) is really messy and keeping track of the order of ALL
focusable elements is very hard.
And if scopes are added it is much easier to track focus that way.

But I think that once you tab one more time on the last element of a scope
thenit should go to the first element in that scope.

That way you can add tabindexscope to forms and all elements of the form
will be loopable.



> And the bug you linked has already been resolved.
>>
>
> It was resolved WONTFIX, but the problem still exists that items in a
> reversed flexbox will tab in non-visual order and it's hard for authors to
> fix it.
>

I don't understand how this is related? just to make a point?
Or to ask someone here to tell you if it is according to the specs or not?

Regards,
Eric
Received on Tuesday, 8 November 2011 13:52:45 UTC

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