Community
Participate
Working Groups
Created attachment 110383 [details] Example contexts.xml file Build ID: I20080617-2000 Steps To Reproduce: 1. create a new dialog, such as new wizard 2. define a help context for it, with a topic that has an href attribute 3. verify that the html file specified by the href displays when the dialog's [?] button is pressed 4. add a description element to the context declaration 5. bring the dialog's help up again More information: The problem is either in ReusableHelpPart.update(IContextProvider, IContext, IWorkbenchPart, Control, boolean), which ignores the context parameter (which has the href topic) when updating its ManagedForm. This is called by DefaultHelpUI.displayContextAsHelpTray(Shell, IContext), which only displays the href topic if context.getRelatedTopics() returned length is 1.
If you have exactly one href and no description the help system will treat this as a special case and open that topic immediately. If there is a description or more than one topic the description and topic list is presented in the tray to the right of the dialog. Is this what you are seeing? If so this is working correctly.
(In reply to comment #1) > If you have exactly one href and no description the help system will treat this > as a special case and open that topic immediately. If there is a description or > more than one topic the description and topic list is presented in the tray to > the right of the dialog. Is this what you are seeing? If so this is working > correctly. It's almost what we're seeing: the problem is that if there is both an href and description, the href is ignored. The topics appear to be a query of the Eclipse documentation, without any reference to our page. Since it's title and heading are the same string being queried, it should be at the top of the results list.
Changing Version tag to something more believable.
This bug has been dormant for a while. Are you still interested in this bug report? If so can you attach one or more screen shots showing the problem.
I'm not working on Eclipse any more, and so am withdrawing this bug.