Bugzilla – Bug 509988
ToolBarButton: buttons on the toolbar should either not have "focusable" state or should gain "focused" state
Last modified: 2009-07-14 19:40:28 UTC
PROBLEM STATEMENT ToolBarButton accessibles currently have the "focusable" state but they do not gain "focus" when they have keyboard focus. I think it only makes sense for ToolBarButton accessibles to gain the "focused" state when they have keyboard focused or not have the "focusable" at all. It is somewhat unclear what the correct behavior would be since IsKeyboardFocusable is "False" for ToolBarButtons in UI Spy on Windows. REPRO 1. Run Accerciser, open the "Interface Viewer" tab, and expand the "Accessible" expander. This will reveal a "States" list. 2. Run uia2atk/test/samples/toolbarbutton.py 3. In Accerciser's left pane, browse to and select the "PushButton" push button accessible. (It is a child of the first "panel" child of the "tool bar" acessible). 4. Use Alt+Tab to return to the "ToolBarButton control" window 5. Press the right arrow, which will cause the "PushButton" to have keyboard focus 6. Check the list of states in Accerciser's interface viewer RESULTS The "PushButton" button has keyboard focus, but the accessible does not have the "focused" state. EXPECTED RESULTS The "PushButton" push button accessible should have the "focused" state. COMMENTS Currently there is a problem manipulating ToolBarButtons with the keyboard. See Bug 509985. It appears that ToolBarButton accessibles can be "toggle button" and "push button", so both of them should be considered. DropDownButtons might also be a special case.
Move all P1 and P2 bugs into Release 1.1 milestone.