W3C home > Mailing lists > Public > public-pfwg@w3.org > October 2014

Re: Proposal to change documentation on tabindex to strongly discourage values greater 0

From: <chaals@yandex-team.ru>
Date: Sat, 18 Oct 2014 01:27:22 +0200
To: "White, Jason J" <jjwhite@ets.org>, Joseph Scheuhammer <clown@alum.mit.edu>, Marco Zehe <mzehe@mozilla.com>, "public-html@w3.org" <public-html@w3.org>
Cc: W3C WAI Protocols & Formats <public-pfwg@w3.org>
Message-Id: <17231413588442@webcorp01e.yandex-team.ru>
17.10.2014, 20:06, "White, Jason J" <jjwhite@ets.org>:
>> -----Original Message-----
>> From: chaals@yandex-team.ru [mailto:chaals@yandex-team.ru]

>> A use case is to build a component that is used in various pages, in
>> different locations, and locally assign tabindex within it, but not have
>> that tabindex override the order of tabbing around the rest of the page.
>>
>> So the requirement *might* be something like being able to scope a set
>> of tabindex attributes, such that they only apply within the scope.
>
> One solution might be a boolean attribute that confines the effect of tabindex attributes of descendant elements to that subtree, and ignores all values of tabindex occurring outside the subtree.

I haven't taken the time to write up a use case in more detail. But at Yandex we build a massive amount of web content (hundreds of millions of views per day) in something like the way I described.

My initial off-the-cuff thinking was some attribute that would scope the tabindex, analagous to the "itemscope" attribute in microdata. Which might be the same as your idea. But perhaps I need to think harder. In the meantime I'll go back to some of the teams who produce these things at Yandex - they might have futher ideas.

cheers

--
Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Friday, 17 October 2014 23:27:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:45:10 UTC