Bug 512261

PROBLEM STATEMENT

A ToolStripComboBox "combo box" accessible has a "menu" accessible child, which has several "menu item" children.  When the combo box is dropped down and the
keyboard is used to navigate to a specific menu item, that menu item accessible
receives the "focused" state despite not having the "focusable" state.  I
assume that the problem is that the menu items should have the "focusable"
state, because the combo box menu items can be navigated to using the keyboard.

Menu item children of the MenuStrip control *do* have the focusable state as expected.

REPRODUCTION STEPS

1.  Run uia2atk/test/samples/toolstripcombobox.py
2.  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.)
3.  In Accerciser's left pane, browse to and select the "12" menu item, which
is a descendant of the combo box accessible.
4.  Use Alt+Tab to return to the combobox_dropdownlist.py application (entitled "ComboBox control")
5.  Press Alt+Down to drop-down the combo box
6.  Click the ToolStripComboBox to drop down the menu
6.  Press the down arrow 2 times until arriving at the "12" menu item
7.  Notice the states in Accerciser's interface viewer (while the combobox_dropdownlist.py application window is still active)

RESULTS

The menu item has the "focused" state, but has no "focusable" state

EXPECTED RESULTS

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

COMMENTS

This actually seems to be a recent regression, because I do not believe the problem existed when I originally reviewed the ToolStripComboBox test on May 13, 2009.

Gtk+ has a similar problem.  I logged a GNOME bug here:  http://bugzilla.gnome.org/show_bug.cgi?id=583748