Bug 471215 - Splitter does not have "focusable" state
Summary: Splitter does not have "focusable" state
Status: REOPENED
Alias: None
Product: UI Automation
Classification: Mono
Component: Winforms - General (show other bugs)
Version: Release 0.9.1
Hardware: All Linux
: P4 - Low : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-30 22:58 UTC by Brian Merrell
Modified: 2010-08-31 14:18 UTC (History)
2 users (show)

See Also:
Found By: Integration Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Merrell 2009-01-30 22:58:56 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
Comment 1 Michael Gorse 2009-03-04 14:53:47 UTC
I'm not sure if it makes sense, either.  However, UIA and gtk/gail both say that a SplitContainer/paned is focusable...
Comment 2 Brad Taylor 2009-03-04 16:50:39 UTC
Going with Mike's opinion here.
Comment 3 Michael Gorse 2009-03-04 17:24:26 UTC
Fixed in UiaAtkBridge R128577.
Comment 4 Brian Merrell 2009-03-19 16:46:10 UTC
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.
Comment 5 Brian Merrell 2009-03-19 16:54:59 UTC
Hrm.. not sure why this was marked INVALID, because the "focusable" state was apparently added to the control.