Bug 198738

Summary: [Viewers] CommonViewer fires a post selection change event when expanding an element in the tree
Product: [Eclipse Project] Platform Reporter: Chris McGee <cbmcgee>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: tom.schindl
Version: 3.3   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
A plugin that demonstrates the problem none

Description Chris McGee CLA 2007-08-02 16:40:08 EDT 
I construct a CommonViewer with the "SWT.SINGLE | SWT.H_SCROLL | SWT.V_SCROLL | SWT.BORDER" flags and no initial selection. After the viewer comes up, I expand one of the root elements and I get a post selection event when I didn't click on any of the tree items. The selection event and the tree have some random selection that I did not click on.

After some debugging it appears that the OpenStrategy has an event listener that is responding to a selection event and firing a post selection event (around line 418).
Comment 1 Boris Bokowski CLA 2007-08-08 08:32:13 EDT 
Do you have a reproducible case (snippet, example plug-in)?
Comment 2 Chris McGee CLA 2007-08-09 16:27:42 EDT 
Created attachment 75795 [details]
A plugin that demonstrates the problem

Make sure that there is at least one project in the workspace.

With the provided plugin open the "Sample View." Notice that nothing is initially selected. Now expand any of the root-level elements in the tree. Notice that although no selection was made, there is a random root-level element that is now selected.

This problem is being noticed on Windows XP SP2 with eclipse 3.3.
Comment 3 Boris Bokowski CLA 2009-11-26 09:49:35 EST 
Hitesh is now responsible for watching bugs in the [Viewers] component area.
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:31:12 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.