Bug 508073

Summary:	MenuStrip: menu loses "focused" and "selected" after mouse clicks and moves away
Product:	[Mono] UI Automation	Reporter:	Brian Merrell <bgmerrell>
Component:	Winforms - General	Assignee:	E-mail List <mono-a11y-bugs>
Status:	VERIFIED INVALID	QA Contact:	E-mail List <mono-a11y-qa>
Severity:	Normal
Priority:	P4 - Low	CC:	cachen
Version:	Release 1.0
Target Milestone:	---
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-29 07:07:32 UTC

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

In Gtk, 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 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 in this case.

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.

Comment 1 Brian Merrell 2009-05-29 07:49:48 UTC

This is very similar to Bug 508079, which deals with ToolStripMenuItem instead of MenuStrip.

Comment 2 Feng Xia Mu 2009-07-02 10:04:46 UTC

in Brian's EXPECTED RESULT: "When using the keyboard to navigate a Gtk example, the "focused" state is added to the menu accessible, only the "selected" state is added. " should be replaced by "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. "

For the gtkmenubar.py, pressing Alt+F to open the "File" menu and pressing down and press right to move to the "foo" menu item,the "selected" state remains on the menu but "focused" state do not.Besides, on the screen, only one 'focused' spot. 

So I think the "EXPECTED RESULT" shoule be :The "File" menu accessible should not lose the "selected" states.

Comment 3 Feng Xia Mu 2009-07-02 10:16:06 UTC

For the gtkmenubar.py, mouse clike the "File" menu ,and then pressing down
and press right to move to the "foo" menu item,the "selected" and "focused" states on the "File" menu all the time.

but I still think "focused" state should add to the "File" menu all the time, because as the cursor moves the focus should change.

Comment 4 Brian Merrell 2009-07-02 16:20:38 UTC

Because of Felicia's helpful comments and my typo in the EXPECTED RESULTS, I logged a new bug (Bug 518827) so that it will be easier for the developers to understand.

Please read this new bug, Felicia.  I believe I included all of the information from your comments in the new bug, but feel free to add comments if I missed something.

Thanks.