Differences in relative paths

[Andrew Poulos]

I have a frameset, index.htm, that's a bit like this:

<script type="text/javascript">
var tp;
window.onload = function() { tp= window.frame["t"]; }
fGotoNewPage = function(loc) { tp.location.replace(loc); }
</script>

<frameset rows="100%,60" cols="*">
<frame src="content/top.htm" name="t" id="t">
<frame src="content/nav.htm">
</frameset>

Where top.htm is basically a blank page. After nav.htm has loaded it
calls fGotoNewPage("blah.htm") to load a new page into 't'.

The folder structure is like this:

index.htm
-- content (a folder)
top.htm
nav.htm
blah.htm
-- scripts (a folder)
nav.js

fGotoNewPage works as expected in FF but IE needs 'content/' prepended
to the file name.

I can understand why IE needs 'content/' perpended (it's a path relative
to index.htm) but why does FF not need it?

Andrew Poulos