Bug 506959

Summary: MenuStrip: Selected state of a menu item persists when the menu item is clicked
Product: [Mono] UI Automation Reporter: Brian Merrell <bgmerrell>
Component: Winforms - GeneralAssignee: E-mail List <mono-a11y-bugs>
Status: NEW --- QA Contact: E-mail List <mono-a11y-qa>
Severity: Normal    
Priority: P2 - High CC: cachen
Version: Release 1.0   
Target Milestone: Release 1.1   
Hardware: x86   
OS: openSUSE 11.1   
Whiteboard:
Found By: Integration Test Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Brian Merrell 2009-05-25 23:39:16 UTC
PROBLEM STATEMENT

When a menu item is navigated to on the keyboard or when the mouse is hovered over it receives the "selected" state.  The problem is that the "selected" state does not go away when the Enter key is pressed or when the item is clicked with the mouse. 

REPRO

1.  Run Accerciser, click on the "Interface Viewer" tab, and expand the
"Accessibles" expander
2.  Run uia2atk/test/samples/toolstripmenuitem.py
3.  In Accerciser, browse to and select the "Open" menu item (under the "File"
menu) of the toolstripmenuitem.py ipy application
4.  Press Alt+F to open the file menu
5.  Press Down to navigate to the "Open" menu item.  (You might want to notice that the "Open" menu item receives the "selected" state as expected.)
6.  Press Enter

RESULTS

The menu closes but notice (in that interface viewer) that the "Open" menu item still has the "selected" state

EXPECTED RESULTS

Pressing enter on the "Open" menu item should result in the accessible losing its "selected" state

COMMENTS

I noticed that the selected menu item does lose its "selected" state when another menu item is selected.  I do not think that is correct, however, because that is not how MenuStrips (MenuBars) work in Gtk, however.  The "selected" state for a menu item on a MenuBar in Gtk+ only appears when that menu item has been navigated to using the mouse or keyboard (or when the menu item is selected with at-spi's selectChild)

You can also duplicate this issue using the mouse.

This is similar to Bug 503733.
Comment 1 Brian Merrell 2009-05-25 23:41:31 UTC
*** Bug 503735 has been marked as a duplicate of this bug. ***
Comment 2 Brad Taylor 2009-07-14 16:08:33 UTC
Move all P1 and P2 bugs into Release 1.1 milestone.