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

Bug 353760

Summary:	Context Help Editor does not refreshes the UI when the source is changed
Product:	[Eclipse Project] PDE	Reporter:	Ankur Sharma <ankur_sharma>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	curtis.windatt.public, Michael_Rennie
Version:	3.7
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug
Bug Depends on:
Bug Blocks:	342868

Description Ankur Sharma

2011-08-03 09:15:06 EDT

This looks like to be a regression due to fix for Bug 342868

Steps to repro in I20110802-2000

1. Create a contest help file
2. Create few Context, topic and command nodes in it.
3. Select a context node in the Definition tab and add some description to it. - say 'desc'
4. A sub-node showing description will appear.
5. Switch to the Source tab
6. Manually remove the <description>desc</description> tag.
7. Switch to Definition Tab

Result: the sub-node showing the description is still there
a) Saving or not saving after step 6 does not have any impact
b) earlier the tree would sync up after some flashing

Similarly modfying the description also does not always shows up the tree.

This problem is also there for the other nodes.


This can get serious as once the UI and source are out of sync, you can continue editing and saving the nodes in the tree and the result will be unpredictable.

Comment 1 Curtis Windatt

2011-08-03 12:07:21 EDT

I'm more willing to live with this regression over having the tree collapse every save.  I'll still mark this for investigation in 3.8.

Comment 2 Ankur Sharma

2011-08-03 12:13:57 EDT

I agree. Thats why did not reopen the original bug.

Comment 3 Eclipse Genie

2018-11-29 14:26:25 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.

--
The automated Eclipse Genie.

Comment 4 Lars Vogel

2019-09-02 14:54:23 EDT

This bug has been marked as stalebug a while ago without any further interaction.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.