[Webkit-unassigned] [Bug 108447] INPUT_MULTIPLE_FIELDS_UI: Focus order is not controllable by tabIndex attribute on <input>

Thu Jan 31 18:17:34 PST 2013

https://bugs.webkit.org/show_bug.cgi?id=108447

--- Comment #3 from Hayato Ito <hayato at chromium.org>  2013-01-31 18:19:35 PST ---
(In reply to comment #0)
> <body>
> <input tabindex=30 value=30>
> <input tabindex=20 type=date>
> <input tabIndex=10 value=10 autofocus>
> </body>
> 
> Steps to reproduce:
>  1. Open the document above on Google Chrome 24+.
>  2. Press TAB 3 times
>    ==> The last sub-field in the date input is focused.
>  3. Press TAB
> 
> Expected:
>   The input with tabindex=30 is focused.
> 
> Actual:
>   The 'Back' navigation button is focused.
> 
> 
> The shadow host of the date input is not focusable, and it's shadow sub-fields are focusable. We have no ways to control focus sequence in this case though the shadow host has tabindex.
> 
> Possible solutions:
>   A) Introduce special handling to respect tabindex on non-focusable shadow host
>   B) Make the shadow host <input> focusable
>      In this case, we'd like to focus on the first sub-field when the shadow host is focused, and Shift+TAB on the first sub-field should skip focusing on the shadow host. We need another hack to detect focus direction.

B) was what I had implemented before. I called it 'focus delegation'.
But I've removed that to prefer a general rule defined in the spec.

I think we need a hack to keep a compatibility for built-in elements, such as input elements, which has a shadow tree unless we can have a good spec to cover this case.

>   C) Stop using shadow DOM focus navigation.
>     Make the shadow host <input> focusable, and make sub-fields non-focusable.
>     We can emulate the current behavior by detecting focus direction.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.