311975 - inconsistent handling of backslash in local filesystem URI

Status: RESOLVED WORKSFORME

(Core :: Networking: File, defect, P5)

Description

[Matt]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

Backslashes are treated as path separators (in a file:// URI) everywhere except
for the final one in the string, which causes strange behaviour. This behaviour
seems inconsistent to me; it should either always be a path separator, or never
be one.




Reproducible: Always

Steps to Reproduce:
1. Create a file C:\foo\bar\qux.html that has some text, and refers to another
file in the same directory (eg. <IMG src="qux.jpg">).
2. Access the file with file://C:\foo/bar\qux.html

Actual Results:  
The text from qux.html was displayed but the image was not. In fact, Firefox
tried to load C:\foo\qux.jpg .


Expected Results:  
It should either load the HTML and the image, or load neither.

The URI file://C:\foo\bar/qux.html does work as expected (page loads and image
loads).

I have read bug 32895 which says that blackslash should be supported for
filesystem locations, but bug 263916 says that it shouldn't. But either way, I
don't think half-and-half is a great solution.

Comment 1

[OstGote!]

I guess, the part after "/" is treated as files under root (because it is the
correct path separator), so Moz tries in the 1st case to load the mentioned
wrong link. In the 2nd link that works, because it is the right dir. 

Comment 2

[Darin Fisher]

-> default owner

Comment 3

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 4

[Valentin Gosu [:valentin] {{ PTO 3 July - 3 August }}]

Backslash normalization works according to spec.
I've tested the scenario in comment 0 and it now works.