Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 258737 - Can't delete bookmarks except via marker in editor
Summary: Can't delete bookmarks except via marker in editor
Status: RESOLVED DUPLICATE of bug 241384
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-13 16:36 EST by James C. Georgas CLA
Modified: 2008-12-14 01:09 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James C. Georgas CLA 2008-12-13 16:36:43 EST
Build ID: I20080617-2000

Steps To Reproduce:
1. bookmark a file from a navigator view
2. in the bookmarks view, delete the bookmark from the context menu, or with the <delete> key.
3. confirm the delete action in the resulting confirmation dialog.
4. note that the bookmark still exists.


More information:
The only way I have been able to delete a bookmark is by removing it from the left hand marker bar in an editor, either by double clicking on the marker, or using the marker's context menu.

A bookmark created by selecting a file in a navigation view and then selecting "Add Bookmark..." from the main "Edit" menu may have no line number associated with it, which means it will not have an icon in the file's marker bar. In this case, I can't remove the bookmark at all.

I would randomly guess that it's an unattached callback on the OK button of the Delete action's confirmation dialog.
Comment 1 James C. Georgas CLA 2008-12-13 16:56:48 EST
Actually, the same problem exists for tasks (but I can work around it by marking a task as completed and then selecting the task view's context menu to delete completed tasks).
Comment 2 Remy Suen CLA 2008-12-14 01:09:58 EST
Sounds like bug 241384. James, please get a 3.4.1 / Service Release 1 build and try again.

*** This bug has been marked as a duplicate of bug 241384 ***