Bug 602350

Summary:	difference implementation of IsEnabledProperty in Windows when the frame is not actived
Product:	[Mono] UI Automation	Reporter:	calen chen <cachen>
Component:	at-spi-sharp	Assignee:	E-mail List <mono-a11y-bugs>
Status:	NEW ---	QA Contact:	E-mail List <mono-a11y-qa>
Severity:	Normal
Priority:	P4 - Low
Version:	Unspecified
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

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!