On Friday 2014-07-25 00:19 +0200, Charles McCathie Nevile wrote:
> Having 32k items in a page doesn't seem like the real-world problem
> would be numbering the tabindex, but the fact that there are 32k
> active things you're trying to manage in a single ordered list…
Having a notion of scoping for
On Thu, 24 Jul 2014 08:10:55 +0200, Jukka K. Korpela
wrote:
2014-07-24 8:34, Boris Zbarsky wrote:
On 7/24/14, 1:29 AM, Jukka K. Korpela wrote:
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
On 7/24/14, 3:13 PM, Jukka K. Korpela wrote:
So how have authors handled the issue in the current situation where
browsers fail to support tabindex values > 32767 and do that
inconsistently?
By not using tabindex on those forms and possibly having sucky keyboard
navigation.
Having that many
2014-07-24 17:24, Boris Zbarsky wrote:
Are there any use cases for tabindex values greater than 32767?
We've seen use cases for forms with that many form controls (large forms
parts of which get conditionally shown/hiden based on values filled in
for some of the controls), so I would think so,
On 7/24/14, 2:10 AM, Jukka K. Korpela wrote:
I’m afraid the fix does not work.
Sure it does.
Testing the jsfiddle code there,
http://jsfiddle.net/tatesn/hVv72/
in the newest Firefox (31.0, on Win 7)
The "newest Firefox" you should be testing in for everything except
"what do shipping UAs d
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, thi
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.
S
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
The tabindex attribute is defined so that its value must be a valid
integer. No other restrictions are currently imposed.
However, browsers actually impose an upper limit of 32767 (which is in
accordance with HTML 4.01:
http://www.w3.org/TR/html401/interact/forms.html#adef-tabindex ).
In Chro
