Bug 107893 - [Help] Dynamic Help: CSS & Relative Paths
Summary: [Help] Dynamic Help: CSS & Relative Paths
Status: RESOLVED DUPLICATE of bug 200031
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 3.2   Edit
Hardware: All Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: platform-ua-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-24 12:47 EDT by Rich Watts CLA
Modified: 2007-09-21 15:17 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rich Watts CLA 2005-08-24 12:47:46 EDT
We have a content repository that we are trying to bind to the Dynamic Help 
panel. When we do, we see that the CSS defined for the help panel is different 
than what is used for our content (it also seems different than what we use in 
the help system). 

We need a way to define or override this behavior.

Second issue but related is that all pages that are loaded are relative to the 
help system not the repository added as an extension point. 

Users also have the ability to set a preference that determines if a Help 
document is loaded in place, or in the editor area. Currently our repository 
use the Help System’s preferences, so this setting will apply to our pages as 
well.  Again the problem here is that the CSS and images are relative to the 
our repository, but the page is loaded to be relative to the help servlet.
Comment 1 Chris Goldthorpe CLA 2007-06-12 16:57:48 EDT
I looked into this a little and have a couple of different ideas as to what might be going on. When I created a help plugin in my workspace ane referenced a CSS file from another workspace project that worked OK. One thing I noticed however was that the Eclipse supplied CSS was being included after the user supplied CSS which means that your CSS can be overridden unless you add 
!important to the lines in your CSS file. I don't know if this is your problem, are you still seeing this problem?
Comment 2 Chris Goldthorpe CLA 2007-09-21 15:17:30 EDT
The first issue, the ability to change the path to the css file inserted into the help view is fixed in 3.3M2, see Bug  200031. 

The second issue I believe can be solved if your use PLUGINS_ROOT/plugin_name in your css path.

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