Bug 578523 - Tree nodes sometimes don't fire IsSelected PropertyChange events
Summary: Tree nodes sometimes don't fire IsSelected PropertyChange events
Status: NEW
Alias: None
Product: UI Automation
Classification: Mono
Component: Winforms - UIA (show other bugs)
Version: Unspecified
Hardware: All Linux
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-09 21:49 UTC by Michael Gorse
Modified: 2010-02-09 21:54 UTC (History)
0 users

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


Attachments
Test case. (2.03 KB, patch)
2010-02-09 21:54 UTC, Michael Gorse
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Gorse 2010-02-09 21:49:55 UTC
If a tree node is selected, then another node is selected, then the first node is re-selected, the first node will not fire an IsSelected event the second time it was selected.  The event is potentially fired when the node provider receives an AfterSelect event.  The event then decides whether to fire by looking at its cached old property value and comparing it with the new value.  Since AfterSelect is only ever called after the node has been selected, the new value will always be true, so the old value will become true and will never be reset to false when the node is deselected, so, on subsequent calls, the BaseAutomationPropertyEvent code will not fire the event since it thinks that the node was already selected.
Comment 1 Michael Gorse 2010-02-09 21:54:00 UTC
Created attachment 341625 [details]
Test case.