Bug 121335 - AX: elements with explicit tabindex should expose AXFocused as writable, since mouse clicks can focus it
Summary: AX: elements with explicit tabindex should expose AXFocused as writable, sinc...
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: chris fleizach
Keywords: InRadar
Depends on:
Reported: 2013-09-13 17:39 PDT by James Craig
Modified: 2013-10-29 09:38 PDT (History)
8 users (show)

See Also:

patch (9.37 KB, patch)
2013-10-28 16:55 PDT, chris fleizach
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description James Craig 2013-09-13 17:39:57 PDT
AX: despite it being removed from the tab order, elements with tabindex="-1" should have their AXFocused state expose as writable (W), since mouse clicks can focus the element.

Test case:
Comment 1 Radar WebKit Bug Importer 2013-09-13 17:40:09 PDT
Comment 2 James Craig 2013-09-13 17:41:43 PDT
In other words, keyboard tab nav would not cause it to be focused, but the VoiceOver cursor landing on this element would cause focus to be set if VOU pref set focus to follow VO.
Comment 3 James Craig 2013-09-13 17:49:19 PDT
This also needs to work for tabindex="0" and tabindex="1", "2", nā€¦

Comment 4 James Craig 2013-09-13 18:00:45 PDT
Blocks UAIG test cases 5, 6, and 9
Comment 5 chris fleizach 2013-10-28 16:55:44 PDT
Created attachment 215348 [details]
Comment 6 Mario Sanchez Prada 2013-10-29 03:01:09 PDT
Comment on attachment 215348 [details]

We'll maybe need some tuning for the GTK/EFL ports but I'm happy with getting this in now and checking later if it's needed or not
Comment 7 WebKit Commit Bot 2013-10-29 09:38:25 PDT
Comment on attachment 215348 [details]

Clearing flags on attachment: 215348

Committed r158195: <http://trac.webkit.org/changeset/158195>
Comment 8 WebKit Commit Bot 2013-10-29 09:38:28 PDT
All reviewed patches have been landed.  Closing bug.