IIRC the spec used to clamp on 16-bit short range (up to 32767).
I haven't researched much yet, but quick search found some links:
http://stackoverflow.com/questions/24924851/when-does-tabindex-xxxx-break
> Browsers actually enforce the limit, though in incompatible ways.
> Chrome and Firefox interpret larger values as 32767 or (for very large
> numbers) 0, IE as negative numbers (except that 32768 is taken as 0).
https://msdn.microsoft.com/en-us/library/ms534654(v=vs.85).aspx
> For Internet Explorer 5.01 or above, the attribute may be set to any
> value in the valid range of -32767 to 32767
I think changing the limit will not have big compat issue, as such large
tabindex are rarely used, or not useful at all. I think this change is
not urgent (so P3 seems appropriate).
Could you clarify the implications for compat issue, e.g. other browsers' behavior, when the spec was updated, etc?
@rob.buis thanks for the research!
As Mozilla and WebKit already does this, it seems safe to ship this in
Chrome.
As this is a web-exposed change, it makes sense to send a note
(in Intent to Implement and Ship format) to blink-dev. Could you work on this?
You seem to have all information to fill in the format:)
Comment 1 by rob.b...@samsung.com
, Oct 11 2016Status: Assigned (was: Untriaged)