1824805 - Different sequential focus behaviour than Chrome

Status: NEW

(Core :: DOM: Core & HTML, defect)

Description

[Sean Feng [:sefeng211]]

We have a different behaviour than Chrome of selecting the next sequential focus element when the current focused element is not in Document's sequential focus navigation order.

STR:

1. Open https://jsfiddle.net/vjqcrkxa/2/
2. Click focus the last input
3. Press <tab>

Firefox moves the focus to <input tabindex=1/> and Chrome moves the focus to <input tabindex=0/>.

I think this scenarios falls into the selection mechanism is DOM + direction is forward of https://html.spec.whatwg.org/multipage/interaction.html#sequential-navigation-search-algorithm, so we should find the first suitable sequentially focusable area in the home document following starting point, but starting point is not a sequencial focusble area, so I am confused.

Emilio, do you know which behaviour is correct?

Comment 1

[Emilio Cobos Álvarez [:emilio]]

Attachment: test-case from comment 0, with text for reference.

Comment 2

[Emilio Cobos Álvarez [:emilio]]

Not off-hand. Olli is more familiar with our tabindex implementation. I know we have different navigation starting point from Chrome generally (we just use selection focus point and chrome uses something more bespoke).

Comment 3

[Olli Pettay [:smaug][[e-mail]]]

I'd expect the behavior Firefox has.

Nothing requires "starting point" to be "sequentially focusable area". The sentence just talks about document of starting point, no?

Comment 4

[Sean Feng [:sefeng211]]

I filed https://github.com/whatwg/html/issues/9081 to clarify this.