Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 103730

Summary:	[Workbench] Navigation History holds histories that aren't valid
Product:	[Eclipse Project] Platform	Reporter:	Ryan L. Cox <rlcox>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	daniel_megert, Silenio_Quarti, tpew
Version:	3.1	Keywords:	helpwanted
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Ryan L. Cox

2005-07-13 17:53:28 EDT

After deleting a project in the workbench, the Navigation History will still 
contain a reference to an editor that was opened on a file in that project. 
The file no longer exists, so when you try to navigate the history (clicking 
the back button) the editor comes up with an error. This is killing some of 
our editors because of the way that they are written. 

I need a way to either remove an item from the history myself (this would 
really be useful for more reasons than just this one) or for the history to 
clean up when deletes happen.

I would really prefer an API to remove items from the navigation history.

Comment 1 Dani Megert

2005-07-18 07:06:08 EDT

Not sure about the new API. We should check whether the entry is valid or not in
the first place. This has to be done in Platform UI since clients don't know how
the input is stored (managed by NavigationHistoryEntry). Clients like the
TextSelectionNavigationLocation only provide additional infor like text positions.

Comment 2 Tod Creasey

2006-04-15 15:12:50 EDT

Is this still an issue in 3.2?

Comment 3 Dani Megert

2006-04-18 04:30:32 EDT

>Is this still an issue in 3.2?
Why not simply try the steps in comment 0? ;-)

Comment 4 Tim Pew

2008-09-04 14:35:14 EDT

This is still a problem in Eclipse 3.4.

Comment 5 Remy Suen

2012-01-27 11:53:20 EST

*** Bug 369960 has been marked as a duplicate of this bug. ***

Comment 6 Lars Vogel

2019-11-14 03:49:41 EST

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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.