Bug 518827

PROBLEM STATEMENT

The root menus on a menu bar (e.g., "File" and "Edit" on the toolstripmenuitem.py sample) have the "focused" and "selected" states after being clicked on.  This is expected (well, sort of, see COMMENTS), but the problem is that when the mouse leaves the component boundaries of the accessible, the accessible loses the "focused" and "selected".  This does not occur in Gtk.

REPRO

1.  Run Accerciser, open the "Interface Viewer" tab, and expand the "Accessible" expander
2.  Run uia2atk/test/samples/menustrip.py 
3.  In Accerciser's left pane, browse to and select the "File" menu accessible
4.  In the menustrip.py application, left-click on the "File" menu.  Notice in the interface viewer that the accessible gains the "focused" and "selected" states.
5.  Move the mouse down to the "New" menu item (but do not click)

RESULTS

The "File" menu accessible loses the "selected" and "focused" states

EXPECTED RESULTS

I would expect that the "File" menu accessible loses the "focused" state, but  keeps the "selected" state.  However...

In Gtk (using these REPRO steps for gtkmenubar.py), both the "selected" and "focused" states remain on the menu accessible.  When using the keyboard to navigate the menustrip.py sample (i.e., pressing Alt+F to open the "File" menu and pressing the down arrow to move to the "New" menu item) the "selected" and "focused" states also remain on the menu.  When using the keyboard to navigate a Gtk example, the "focused" state is not added to the menu accessible, only the "selected" state is added.  Basically, nothing is very consistent, but I would expect at least the "selected" state to stay on the "File" menu accessible with the REPRO steps above.

I definitely think our behavior should be the same regardless if the mouse of keyboard are used to navigate.  Gtk+ is inconsistent in this regard, but I believe that it is probably a bug on their part.