Bug 505493 - ToolStripSplitButton: Extraneous "selected" and "focused" states after performing 'click' action on a menu item
Summary: ToolStripSplitButton: Extraneous "selected" and "focused" states after perfor...
Status: NEW
Alias: None
Product: UI Automation
Classification: Mono
Component: Winforms - General (show other bugs)
Version: Release 1.0
Hardware: x86 openSUSE 11.1
: P3 - Medium : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-20 03:34 UTC by Brian Merrell
Modified: 2009-07-02 03:40 UTC (History)
1 user (show)

See Also:
Found By: Integration Test
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 Brian Merrell 2009-05-20 03:34:42 UTC
PROBLEM STATEMENT

After using the at-spi 'click' action on one of the ToolStripSplitButton menu items, that menu item has the "focused" and "selected" states.  This should not be the case (as the Bridge functional spec indicates that a click action results in -focused and -selected states).

REPRO

1.  Run Accerciser, open the "Interface Viewer" tab, and expand the "Accessible" and "Action" expanders.
2.  Run uia2atk/test/samples/toolstripsplitbutton.py
3.  In Accerciser's left pane browse to and select one of the "menu item" accessibles from the toolstripsplitbutton.py (ipy) application
4.  In Accerciser's interface viewer, perform the 'click' action for the selected menu item accessible (by selecting the 'click' action and pressing "Perform action")
5.  Notice the states of the selected accessible in the "States" list of Accerciser's interface viewer 

RESULTS

The selected accessible has both the "selected" and "focused" states

EXPECTED RESULTS

The selected accessible should not have the "selected" or the "focused" state
Comment 1 Ray Wang 2009-05-21 03:29:12 UTC
em,I'm not sure is there any interrelationship between this bug and bug 465597, just mentioned here as a reference. :)