Insert a script block like: <script src="/foo/bar.js"></script> in a file placed in a subdirectory (ie: /some/directory) When you look in the top-left (file exploring) pane in the debugger and locate the script, the URL is wrong- it comes out as http://server/some/directory//foo/bar.js and the file can't be found.
we should set the script filename to the full path, not the value of the src attribute.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → mozilla1.0
...actually, we do. I didn't notice you were talking about the top left view. You are talking about the *top* left view, the one with "Windows" and "Breakpoints" in it, right? Regardless, both top left and middle left views correctly resolve relative scripts for me. Reporter, are you still seeing this?
It's actually the top-right frame. It displays an error page from the webserver because it is trying to resolve a JS file that doesn't exist. I'll grab the latest nightly and re-confirm.
Yeah- still happens. Some other possibilities: I'm using a frameset One frame references a script like so: <script src="/aspnet_client/1_0_0_0/xxx.js"></script> This root URL is appended to the path, rather than replacing the path to the frame and appears in the window like: "http://localhost/prototype/petroLook/frameset//aspnet_client/1_0_0_0/xxx.js" It should be: "http://localhost/aspnet_client/1_0_0_0/xxx.js"
*** Bug 130566 has been marked as a duplicate of this bug. ***
I'll add a me too, and a vote, since this bug is a real pain. I'm getting this bug on win2k, build 2002041711. The source frame shows a 404 message like: <H1>Not Found</H1> The requested URL /mylibrary//includes/topmenus.js was not found on this server.
Confirming for Build 2002060408 / WinNT4 (and adding a vote).
*** Bug 154749 has been marked as a duplicate of this bug. ***
This should (finally) be fixed. Get the latest mozilla nightly or an XPI from <http://www.hacksrus.com/~ginda/venkman/>.
Status: ASSIGNED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.