Bug 496786 - ListBox: click action for TableCell doesn't send event to change lable
Summary: ListBox: click action for TableCell doesn't send event to change lable
Status: REOPENED
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-04-21 08:29 UTC by calen chen
Modified: 2009-07-15 03:49 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
pyatspi script to click table cell (552 bytes, text/x-python)
2009-07-15 03:49 UTC, calen chen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description calen chen 2009-04-21 08:29:28 UTC
REPRO:

1. run uia2atk/test/samples/listbox.py
2. mouse click table cell 1, lable is changed to "You select 1"
3. run accerciser, expand tree table, browse to table cell 5
4. under interface vieser, expand Action, doing click

RESULTS:

after doing step 4, table cell 5 is selected and focused, but lable still remain "You select 1"

EXPECTED RESULTS:

lable should be changed to 'You select 5', in this example click action not only select tablecell but also send event to change lable

COMMENTS:

BTW, it can work well if change Click event to SelectedIndexChanged event in listbox.py
Comment 1 Brad Taylor 2009-07-14 16:08:27 UTC
Move all P1 and P2 bugs into Release 1.1 milestone.
Comment 2 Brad Taylor 2009-07-14 17:49:12 UTC
This might be an accerciser issue.  Calen, can you come up with a pyatspi test for this to isolate Accerciser from the equation?  Thanks!
Comment 3 calen chen 2009-07-15 03:49:14 UTC
Created attachment 305126 [details]
pyatspi script to click table cell

Hi Brad, here is a pyatspi script, I call pyatspi doAction(0) to click table cell 5 that also can't send event to change label, so it seems not be an accerciser issue, please take a look, thanks!