🚀 go-pugleaf

I know of this problem, here is how i tried to explain it in an onther posting
(this was about changing images in other frames - basically it's the same
problem):

>>>>Pasting the posting:
Well, this is one of these things that would drive you mad. I encoutered the
same problem a few years ago. But i still having nightmares because off it. It
is one of the
reasons why i dislike some products and some companies.

First i like to state that if you wouldn't use directories, but just one
folder, offcourse you wouldn't have this problem. Also, if you do use
directories, and give full
blown URL's for changing locations (URL, SRC), there is no problem. (But,
offcourse, if you have a complex site you want directories, and you want to use
relative
URL, as you want to test your site offline.)

What is the actual problem then? That is: what is a relative URL relative to.
Let's say we have index.html in the root. It represents a frameset with two
frames: frame1 containing document1.html, and frame2 containing document2.html.

In the same root there is a folder called somepages, containing the documents
document1.html and document2.html.
We also have a second folder that is called images, which contains image.gif
and otherimage.gif.
Let's say image.gif appears in document1.html on default, and you would like to
replace it by otherimage.gif by means of javascript, using a relative URL. The
script is called from document2.html.

In Netscape the code should be:
    parent.frame1.document.images[0].src = "../images/otherimage.gif";
(You should know that ../ means go one up in the directorystructure)
In Explorer the code should be:
    parent.frame1.document.images[0].src = "images/otherimage.gif";

This means that Netscape is interpreting the URL relative to the document.
Hence, we have to move one up (../) before entering the folder images.
Explorer came with an other interpretation. It says the URL should be relative
to the frameset, that is to the document index.html that is in the root. In
this
interpretation the move one up is offcourse false and ../ should be left away.

Solution for this is to make a filter:
--------
     var browser = navigator.appName
     if(browser.indexOf("Micros") != -1){
         var strange = "";
     }
     else{
         var strange = "../";
     }
     parent.frame1.document.images[0].src = strange + "images/otherimage.gif";
----------

Isn't all off this strange....

>>>>>>End of posting

Hope this will help you,
Peter Baaij