W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2014

Re: [whatwg] Maximum value needed for tabindex

From: Olli Pettay <olli@pettay.fi>
Date: Thu, 24 Jul 2014 16:04:27 +0300
Message-ID: <53D1045B.6080906@pettay.fi>
To: whatwg@lists.whatwg.org
On 07/24/2014 09:10 AM, Jukka K. Korpela wrote:
> 2014-07-24 8:34, Boris Zbarsky wrote:
>
>> On 7/24/14, 1:29 AM, Jukka K. Korpela wrote:
>>> However, browsers actually impose an upper limit of 32767
>> ....
>>> In Chrome and Firefox, values larger than this are interpreted as 0.
>>
>> In the case of Firefox, this was a bug, that was fixed a few months ago.
>>   See https://bugzilla.mozilla.org/show_bug.cgi?id=996095
>
> I’m afraid the fix does not work. Testing the jsfiddle code there,
> http://jsfiddle.net/tatesn/hVv72/
> in the newest Firefox (31.0, on Win 7),

The patch landed for FF32.


the “Click here” link, with tabindex="40000", and the input element after it, with tabindex="200007", are not
> in the tabbing order at all, and the tabIndex property value is 32767. This is odd because tabindex="32767" as such works OK.
>
> My observation on larger values being taken as 0 was based on my initial testing with very large values (outside Int32 range).
>
> In Chrome, the elements are in the tabbing order, but if their tabindex attributes are swapped, the order stays the same, i.e. follows the textual
> order. This is natural since tabIndex property value is 32767 for both.
>
>>> 1) Keep tabindex unlimited and try to make browsers implement this.
>>
>> This is what we should do, in my totally biased opinion.
>
> Even in the best case, it would take several years before the usage share of all current browser versions is small enough.
>
> Are there any use cases for tabindex values greater than 32767? Presumably not real use now (since such values do not work), but are there reasonably
> imaginable use cases?
>
> Yucca
>
>
Received on Thursday, 24 July 2014 13:05:00 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:21 UTC