Bug 504655 - at-spi 'click' action cannot be used to select a color from the ColorDialog
Summary: at-spi 'click' action cannot be used to select a color from the ColorDialog
Status: NEW
Alias: None
Product: UI Automation
Classification: Mono
Component: Winforms - General (show other bugs)
Version: Release 1.0
Hardware: x86 openSUSE 11.1
: P2 - High : Normal
Target Milestone: Release 1.1
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-18 07:12 UTC by Brian Merrell
Modified: 2009-07-14 17:54 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-18 07:12:10 UTC
PROBLEM STATEMENT

A ColorDialog presents several colors for selection.  The colors are presented to the user in the dialog in the form of buttons.  The desired color button is clicked and then the dialog's OK button is pressed to select a color.  The problem is that the at-spi click action cannot be used to successfully select a color.

REPRO

1.  Open Accerciser, click on the "Interface Viewer" tab, and expand the "Action" expander.
2.  Run uia2atk/test/samples/colordialog.py and click on the "ColorDialog Button" button.  Notice that red is selected by default.
3.  In Accerciser's left pane, browse to and expand the panel accessible that has 66 children.  This is the panel that contains all of the color buttons.  
4.  In Accerciser, select any one of the base color buttons--except red--that is a child of the panel from step 3.
5.  Perform the 'click' action in Accerciser's interface viewer (by selecting the 'click' action and pressing "Perform Action")
6.  Click "OK" in the "Color" dialog

RESULTS

The label on the "ColorDialog control" window reads:  "Color [Red]"

EXPECTED RESULTS

The label on the "ColorDialog control" window should contain text about the color for which the 'click' action was performed in REPRO step 5.

COMMENTS

I believe this is caused by Bug 504593, but I wanted to log a separate bug in case it is not.
Comment 1 Brad Taylor 2009-07-14 16:08:32 UTC
Move all P1 and P2 bugs into Release 1.1 milestone.