Bugzilla – Bug 471215
Splitter does not have "focusable" state
Last modified: 2010-08-31 14:18:49 UTC
PROBLEM STATEMENT The Splitter control does not have a "focusable" state. However, it should, according to the Bridge specification[1] REPRO 1. Run Accerciser, open the "Interface Viewer" tab and expand the "Accessible" expander. 2. Run uia2atk/test/samples/splitter.py 3. In Accerciser's left pane, browse to and select the accessible with the "split pane" role. This accessible represents the Splitter control. RESULTS The list of states in the interface viewer tab shows that the split pane accessible does not have a "focusable" state. EXPECTED RESULTS According to the spec, the split pane accessible should have the "focusable" state. COMMENTS This could be a problem with the spec. Should Splitter really be focusable? [1] http://www.mono-project.com/Accessibility:_Bridge_Functional_Specification
I'm not sure if it makes sense, either. However, UIA and gtk/gail both say that a SplitContainer/paned is focusable...
Going with Mike's opinion here.
Fixed in UiaAtkBridge R128577.
Not sure open this fix. I am reopening. UISpy shows 'IsKeyboardFocusable: "False"' for the splitter accessible. Even when you select our splitter with the mouse it doesn't become focusable, so I don't really see the point. Reopening for feedback.
Hrm.. not sure why this was marked INVALID, because the "focusable" state was apparently added to the control.