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: https://dvcs.w3.org/hg/pfwg/raw-file/default/ARIA-UAIG/1.0/tests/test-files/test2.html
<rdar://problem/14990949>
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.
This also needs to work for tabindex="0" and tabindex="1", "2", n⦠https://dvcs.w3.org/hg/pfwg/raw-file/default/ARIA-UAIG/1.0/tests/test-files/test3.html
Blocks UAIG test cases 5, 6, and 9
Created attachment 215348 [details] patch
Comment on attachment 215348 [details] patch 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 on attachment 215348 [details] patch Clearing flags on attachment: 215348 Committed r158195: <http://trac.webkit.org/changeset/158195>
All reviewed patches have been landed. Closing bug.