Bug 459320 - ToolStripDropDownButton: menu with wrong "selected" state
Summary: ToolStripDropDownButton: menu with wrong "selected" state
Status: VERIFIED DUPLICATE of bug 459332
Alias: None
Product: UI Automation
Classification: Mono
Component: Winforms - General (show other bugs)
Version: Release 0.9
Hardware: x86 openSUSE 11.0
: P2 - High : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-16 08:23 UTC by calen chen
Modified: 2009-01-07 10:19 UTC (History)
0 users

See Also:
Found By: ---
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 calen chen 2008-12-16 08:23:29 UTC
PROBLEM STATEMENT

mouse click ToolstripDropDownButton1 can rise "focused" and "selected" states for menu and show menu list, then move mouse focus to ToolstripDropDownButton2(not click), menu list of ToolstripDropDownButton1 disappear but menu still with "focused" and "selected", unless click ToolstripDropDownButton1 to show menu list again to get rid of "selected"

REPRO:

1. run accerciser
2. run uia2atk/test/samples/toolstripdropdownbutton.py
3. mouse click ToolstripDropDownButton1 in GUI to show menu list
4. in accerciser, expand 'ipy' on the left tree, select ToolstripDropDownButton1 which is with
"menu" role, see states

5. move mouse to ToolstripDropDownButton2 in GUI, menu list of ToolstripDropDownButton1 disappear, see menu[0]'s states

6. mouse click ToolstripDropDownButton1 to show menu list again, see menu[0]'s states

RESULTS:

in step 5: menu[0] still with "focused" and "selected"

in step6: menu[0] get rid of "selected"

EXPECTED RESULTS:

I expect in step5 menu[0] should get rid of "focused" and "selected", because focus is moved to menu[1]

in step6 menu[0] should rise "focused" and "selected" again
Comment 1 Brad Taylor 2009-01-02 12:43:15 UTC
Because of #457990, ToolStripDropDownButton no longer can be focused, so part of this bug has been resolved.  When it comes to the selection, it seems like the real underlying problem is what is described in #459332 -- that both menus can be open at the same time.  This cannot be done as a user, so I don't think you should be able to do it via UIA.

Marking this bug as a duplicate of #459332.  Work on this issue will continue there.

*** This bug has been marked as a duplicate of bug 459332 ***
Comment 2 calen chen 2009-01-06 03:55:06 UTC
hello brad, i think there is a little bit difference, say sorry that the previous description is complicated. please forget "focused", just look at "selected" state. 

step 1: run uia2atk/test/samples/toolstripdropdownbutton.py
step 2: run accerciser, select toolstripdropdownbutton1 with menu role from left tree, see states
step 3: mouse click toolstripdropdownbutton1 in gui window to show menu item list, rise "selected" state is correct
step 4: mouse click blank space or move mouse to toolstripdropdownbutton2(don't click) in gui to close toolstripdropdownbutton1's menu item list, then see toolstripdropdownbutton1's states

the problem is: in step 4, toolstripdropdownbutton1 still with selected

my expectance is get rid of "selected" when menu item list disappear like gtk.menu. please tell me your idea if you have different opinion, thanks :)
Comment 3 Brad Taylor 2009-01-06 14:50:26 UTC
Yes, you're correct -- I can reproduce the steps you have in comment #2.  However, these steps are different than the one in the original bug, so it really needs to be filed as another issue.

Closing as duplicate again.  The new issue is #463814.

*** This bug has been marked as a duplicate of bug 459332 ***
Comment 4 calen chen 2009-01-07 10:19:08 UTC
I think the different steps both produced one issue :) but it's okay, thanks you created a new bug, it looks more clearly:)

Colsed in trunk r122613