Bug 330 - [Chameleon 1.1] relative paths for PopupCSS shared resource not working
: [Chameleon 1.1] relative paths for PopupCSS shared resource not working
Status: CLOSED FIXED
: Chameleon
Core
: 1.99
: PC Windows 2000
: P1 normal
: 1.99 beta 2
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2004-03-29 11:53 by
Modified: 2004-07-06 17:19 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2004-03-29 11:53:17
The path to the css file needs to go through a similar hierarchy as buttonizer
and WaitImage does when looking for the css file specified in the shared resource.

absolute web paths work, ("/msapps/application/popup.css") but relative ones
("skins/flat_grey/popup.css") are looking relative to chameleon, not relative to
the template.

another issue that I'm wondering about, for paths in general, what happens if I
have popup.css in the same folder as the template ("popup.css") will it look
relative to chameleon and use that popup.css or will it look relative to the
template and use that popup.css?
------- Comment #1 From 2004-04-07 12:33:46 -------
to be fixed/reviewed for 1.99 beta
------- Comment #2 From 2004-04-08 08:37:14 -------
updated version to 1.99
------- Comment #3 From 2004-04-14 10:35:41 -------
working on this now
------- Comment #4 From 2004-04-16 08:00:06 -------
it will check relative to the application first and use it, then assume relative
to the chameleon installation.
------- Comment #5 From 2004-04-16 08:10:11 -------
fixed in cvs version ... the code was correct but was being processed in the
wrong order of priority so that the css file would be found in the file system
before it was found relative to a web path.
------- Comment #6 From 2004-06-22 14:37:38 -------
verified using beta 2 2004-06-20 on Windows 2000 IE 6

http://localhost/chameleon/samples/sample_bilingual.phtml

http://localhost/....hawaii demo

All popups are able to find the css file 
------- Comment #7 From 2004-06-30 11:46:14 -------
Fred is it possible to have a methodology to test that this bug is fixed?  I
made a few tests but I am not sure I'm verifying the right thing.  For example I
renamed the "popup.css" in the
"/path/to/chameleon_beta/htdocs/skins/default/css" directory and got no error
when opening samples popup windows.
------- Comment #8 From 2004-07-05 17:00:49 -------
I guess the best way to test this is to have two different css files that have
the same name, but located in different places (with very different styles)

using a relative url in the shared resource eg. "skins/flat_grey/popup.css"

so if there is a css that makes the popups green relative to chameleon, and
another that makes them blue relative to the template, you would know that this
is working if the popups were blue.
------- Comment #9 From 2004-07-06 15:27:33 -------
I need documentation on how to create a popup sharedresource.
------- Comment #10 From 2004-07-06 15:44:07 -------
to add a popup shared resource you need a line like this in your template

<cwc2 type="SharedResource" name="PopupCSS" value="/msapps/demo_app/popup.css"/>

I'd recomend just duplicating the default popup.css that comes with chameleon,
and changing the colours so you can tell the two apart.
------- Comment #11 From 2004-07-06 17:19:37 -------
Verified on Fedora Core 1 Chameleon 20040625 with "sample_enhanced.phtml"
sample.  I added the "<cwc2 type="SharedResource" name="PopupCSS"
value="css/popup.css"/>" line in the "html" file.

It looks first in the application directory then in the chameleon installation
directory.  I followed instructions in comment #8.