Bug 506745 - DropDownList combo box receives "focused" state, but do not have "focusable" state
Summary: DropDownList combo box receives "focused" state, but do not have "focusable" ...
Status: NEW
Alias: None
Product: UI Automation
Classification: Mono
Component: Winforms - General (show other bugs)
Version: Release 1.0
Hardware: x86 openSUSE 11.1
: P4 - Low : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-24 22:49 UTC by Brian Merrell
Modified: 2009-07-02 03:34 UTC (History)
1 user (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-05-24 22:49:45 UTC
PROBLEM STATEMENT

A DropDownList ComboBox control accessible receives the "focused" state, but does not have the "focusable" state.

REPRODUCTION STEPS

1.  Run uia2atk/test/samples/combobox_stylechanges.py
2.  Click on the "DropDownList" button of the combobox_stylechanges.py application.  (The default ComboBox style of the combobox_stylechanges.py application is "DropDown", which doesn't have this problem because the combo box is never actually focused).  
3.  Run Accerciser, open the "Interface Viewer" tab and expand the "Accessible"
expander.  (This will reveal the "States" list, which shows the current states
of the selected accessible.)
4.  In Accerciser's left pane, browse to and select the "combo box" accessible
5.  Use Alt+Tab to return to the combobox_stylechanges.py application (entitled "ComboBox Style Changes")
6.  Press Tab until the keyboard focus arrives at the ComboBox
7.  Notice the states in Accerciser's interface viewer (while the combobox_stylechanges.py application window is still active)

RESULTS

The combo box has the "focused" state, but has no "focusable" state

EXPECTED RESULTS

I would expect the menu item to have the "focusable" state

COMMENTS

Gtk+ has the same behavior we do.  I logged a GNOME bug here:  http://bugzilla.gnome.org/show_bug.cgi?id=583749