New issue
Advanced search Search tips

Issue 642267 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Sep 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Default value of tabIndex IDL attribute for FIELDSET and OUTPUT

Reported by taken....@gmail.com, Aug 30 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2843.0 Safari/537.36

Example URL:

Steps to reproduce the problem:
HTML Standard says that default value is 0 for elements that are focusable and −1.
https://html.spec.whatwg.org/multipage/interaction.html#dom-tabindex

Some non-focusable elements (listed below) return 0 for tabIndex.

a without href
input[type=hidden]
input[disabled]
select[disabled]
textarea[disabled]
button[disabled]
filedset
output

What is the expected behavior?
Non-focusable elements should return -1 for tabIndex

What went wrong?
Non-focusable elements return 0

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? No 

Does this work in other browsers? Yes 

Chrome version: 55.0.2843.0  Channel: canary
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0

It may be too late to change default valule of following elements as Firefox, Edge and Safari return 0 for years.

a without href
input[type=hidden]
input[disabled]
select[disabled]
textarea[disabled]
button[disabled]

Firefox returns -1 for fieldset and output
 

Comment 1 by taken....@gmail.com, Aug 30 2016

Testcase
default-tabindex-chromium.html
2.0 KB View Download

Comment 2 by e...@chromium.org, Aug 30 2016

Components: -Blink Blink>Forms

Comment 3 by tkent@chromium.org, Aug 30 2016

Labels: -Pri-2 Hotlist-Interop Hotlist-GoodFirstBug OS-Android OS-Chrome OS-Linux OS-Mac Pri-3
Status: Available (was: Unconfirmed)
Summary: Default value of tabIndex IDL attribute for FIELDSET and OUTPUT (was: default value of tabIndex for non focusable elements)
Yeah, we shouldn't change the interoperable behavior.  So this bug should handle only <fieldset> and <output>.

Comment 4 by lunalu@chromium.org, Aug 31 2016

Owner: lunalu@chromium.org
If no one else is working on this, I'd like to contribute. 
I made a fix on this, not sure if I did it correctly. Could someone please take a look at it?
https://codereview.chromium.org/2298133004/
Thanks

Comment 6 Deleted

Comment 8 by tkent@chromium.org, Sep 2 2016

Labels: M-55
Status: Fixed (was: Started)
Status: Verified (was: Fixed)
Owner: loonyb...@chromium.org

Sign in to add a comment