348915 - file:// versus file:///

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Dori]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6

I imagine it must be a dupe but I tried searching for this and couldn't find it. Firefox 1.0.x understands file:// for local files, whereas Firefox 1.5.x understands only file:///. To me this seems like a bad idea as it breaks Firefox 1.0.x links, and there is no way to create links that work for both versions of firefox. Given that most people use file:// for I.E. links, it seems like Firefox should have maintained this convention.

Reproducible: Always

Comment 1

[sendmail.to]

Fx1.5.0.6
I created a testcase like that: 
<a href="file://C:/test.html" >Link</a>

And it works fine, Fx repairs the URI to file:///C:/test.html

Comment 2

[Dori]

I hadn't noticed, but the links are actually shares, so they would be of the form: file://example/test.html

Comment 3

[sendmail.to]

For a network share typing 
\\127.0.0.1/test/
into URL Bar

Fx repairs URI to file://///127.0.0.1/test/

could you please test the two possibilities on your Fx 1.x

Comment 4

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 5

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.x 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.