Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 325583 - [CSS] Image paths must be relative to contributing CSS
Summary: [CSS] Image paths must be relative to contributing CSS
Status: RESOLVED WORKSFORME
Alias: None
Product: e4
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 1.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-17 09:10 EDT by Thomas Schindl CLA
Modified: 2019-06-05 07:46 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 Thomas Schindl CLA 2010-09-17 09:10:58 EDT
Currently image paths are resolved using special IResourceLocators which works good for applications controled by a small group of persons but provides problems in multi-plugin systems like Eclipse.

Take the following example:

--------8<--------
org.company1
  + css/
    my.css (image: url(css/image/companyicon.png))
    + images
      companyicon.png
org.company2
  + css/
    my.css (image: url(css/image/companyicon.png))
    + images
      companyicon.png
--------8<--------

Naturally both of them contribute an IResourceHandler to look up the resource . As long as an appliction has only one of those bundles there's no problem but if both are present the problem is the first of them will handle both requests.

I think we need to support relative urls in CSS which are in browsers relative to the css-File the defintion is declared in. For this in case of file based contributions we need to fixup the url to hold the Symbolic-Bundle name and CSS-File location relative to the bundle.
Comment 1 Eclipse Genie CLA 2018-10-25 16:09:21 EDT
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 2 Lars Vogel CLA 2019-06-05 07:46:01 EDT
This is a mass change to close all e4 bugs marked with "stalebug" whiteboard.

If this bug is still valid, please reopen and remove the "stalebug" keyword.