Bug 275863 - [CommonNavigator] Empty project behaves weird in Project Explorer
Summary: [CommonNavigator] Empty project behaves weird in Project Explorer
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 301817 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-05-12 09:20 EDT by Szymon Brandys CLA
Modified: 2019-09-06 16:06 EDT (History)
2 users (show)

See Also:

Attachments
Screenshot illustrating the issue (49.78 KB, image/jpeg)
2009-05-12 09:22 EDT, Szymon Brandys CLA 		no flags Details
View All 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 Szymon Brandys CLA 2009-05-12 09:20:17 EDT 
I found this issues while looking at bug 275859.

Try steps from bug 275859 in the project explorer.

1. Create an empty project in the project explorer
2. Select some files from any project and copy/paste them to the empty project using ctrl+c/ctrl+v
3. Delete the files from the empty project
4. You should see a weird empty node (see the screenshot)
Comment 1 Szymon Brandys CLA 2009-05-12 09:22:49 EDT 
Created attachment 135342 [details]
Screenshot illustrating the issue

Build id: I20090508-2000
Comment 2 Boris Bokowski CLA 2009-05-12 11:51:05 EDT 
I can reproduce this on Mac Cocoa as well.
Comment 3 Francis Upton IV CLA 2009-05-12 12:00:55 EDT 
This one has been around a while, but I can't find the other bug report for it.  I could only make it happen on Windows.
Comment 4 Francis Upton IV CLA 2010-02-08 11:09:48 EST 
*** Bug 301817 has been marked as a duplicate of this bug. ***
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:06:00 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.