Bug 602350 - difference implementation of IsEnabledProperty in Windows when the frame is not actived
Summary: difference implementation of IsEnabledProperty in Windows when the frame is n...
Status: NEW
Alias: None
Product: UI Automation
Classification: Mono
Component: at-spi-sharp (show other bugs)
Version: Unspecified
Hardware: Other Other
: P4 - Low : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-04 11:45 UTC by calen chen
Modified: 2010-05-04 12:01 UTC (History)
0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description calen chen 2010-05-04 11:45:17 UTC 
REPRO:

1. Run winforms app from uia2atk/test/samples/winforms/button_label_linklabel.py, or gtk app from uia2atk/test/samples/gtk/gtkbutton.py
2. click button1 to invoke a message dialog that would make the main frame is not actived
3. run UIAExplorer, navigate button1 on the left tree to see it's IsEnabledProperty value

RESULTS:

IsEnabledProperty shows 'True' when the main frame is not actived

EXPECTED RESULTS:

when message dialog appears that the main frame is not active, then the buttons' IsEnabledProperty(I think each enabled elements such as checkbox in the main frame) should shows 'false' because they couldn't be clicked or checked again. 

COMMENTS:
I have checked this kind of implementation in UIAVerify or UIASpy that would shows 'false' when main frame is not actived,  is it relate to bug596801, would you please take a look? thanks!