444554 - Javascript problem with directories ("../"-problem)

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Udo]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9) Gecko/2008061015 Firefox/3.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9) Gecko/2008061015 Firefox/3.0

If I want to access a file (for example an image) in a higher directory with Javascript, the script doesn't give the correct location.
For example, if I have a page under
/home/user1/files/example/ and want to access the file 
"../picture.jpg", I don't get 
/home/user1/files/picture.jpg but instead 
/home/user1/picture.jpg. 

If I use "./picture.jpg" (one point instead of two points) 
I get the right file , but that doesn't work in Internet Explorer, Opera or any other browser including Firefox 1 and 2.


Reproducible: Always

Steps to Reproduce:
1. document.write an image in Javascript in a higer directory ("../../graphic.gif") with Firefox 1 or 2, Internet Explorer or other browsers
2. Do the same in Firefox 3 (the script wants to access a different location, for example /home/graphic.gif instead of /home/user1/dir1/graphic.gif)
3. "./" works in Firefox 3, but not in other browsers like Firefox 1 or 2 or Internet Explorer

Comment 1

[Jesse Ruderman]

Are you using document.write to create a new document or to insert something into a document as it is being parsed?  Can you attach a complete example that demonstrates the bug?

Comment 2

[Tyler Downer [He/Him]]

This is a mass search for bugs that are in the Firefox General component, are
UNCO, and have not been changed for 800 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10, create a fresh profile,
http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you
still see the bug, please update this bug. If the issue is gone, please set the
resolution to RESOLVED > WORKSFORME.

Comment 3

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.