Closed Bug 1510643 Opened 6 years ago Closed 5 years ago

tabIndex inside shadowRoot breaks tab-ordering

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P2)

63 Branch
Unspecified
Windows
defect

Tracking

()

RESOLVED DUPLICATE of bug 1512043
Tracking Status
firefox63 --- affected
firefox64 --- affected
firefox65 --- affected

People

(Reporter: kenyerr, Assigned: edgar)

References

(Blocks 1 open bug)

Details

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

Steps to reproduce:

Use tabIndex property inside & outside a shadowRoot.

http://embed.plnkr.co/npW8yRXhLGkCV3xmIS1N/

(It is not reproducible with Firefox 57 where of course we have to import the webcomponents-bundle.
But it is also not reproducible even with the Firefox 63 if we import & force enable the polyfills)


Actual results:

The tab order is broken. If the next element would contain a defined tabIndex inside it's shadowRoot then another element will be chosen outside of the current container-element.


Expected results:

The tabIndex values inside the shadowRoot are ignored.
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0   
Build ID: 20181203214946        
I manage to reproduce this on Windows 10 x64 with 65.0a1 (2018-12-03) (64-bit).
Status: UNCONFIRMED → NEW
Component: Untriaged → Keyboard: Navigation
Ever confirmed: true
OS: Unspecified → Windows
Product: Firefox → Core
Edgar, I seem recall that this is a known defect and should have an existing tracking bug?
Blocks: shadowdom
Flags: needinfo?(echen)
Hmm, we have fixed some tab navigation issue for nesting Shadow DOM, but this one looks like another case that doesn't work well.
This probably is a similar issue with bug 1512043.
Assignee: nobody → echen
Flags: needinfo?(echen)
Priority: -- → P2
I will add a test case in bug 1512043.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Component: Keyboard: Navigation → User events and focus handling
You need to log in before you can comment on or make changes to this bug.