90383 - Don't convert backslashes in URIs to forward slashes

Status: VERIFIED WORKSFORME

(Core :: DOM: Navigation, defect)

Description

[Braden]

Why is this done? I thought the conclusion of previous discussions about this
was that Mozilla would be liberal about what it accepted in the location bar,
but respect the specification as far as URIs in documents.

 * I think that whatever the conclusion is, it should be the same for all
platforms. Having links "work" on one platform and be nonfunctional on another
is just silly. It is certainly not consistent with a goal of providing a
platform-independent user experience.

 * Accommodating the Wrong Thing just encourages bad practice; and silently, too.

Comment 1

[Håkan Waara]

-> Embedding: Docshell

Comment 2

[Adam Lock]

I don't believe default URI fixup occurs for link clicks but it definitely does
for the address bar. I should have mentioned that in my npm.general post if that
is what you were responding to.

I will verify with a test case containing various silly URLs.

Comment 3

[Adam Lock]

Attachment: Some bad URLs

Comment 4

[Adam Lock]

Marking WORKSFORME.

The only "bad url" to work is the file://c:\ one. Probably the file URI parser
is doing the conversion for that. The other two are correctly rejected.

Comment 5

[Braden]

Adam: Yup, this is in response to your ng posting. I don't have access to
Windows, so I couldn't test exactly where this occurs. Sorry if I seemed to be
jumping the gun, but I didn't want this to fall through the cracks if it
actually was an issue.

Marking VERIFIED.

(The file: URL thing is probably a side effect of the fact that Mozilla will
accept *anything* in the authority part of a file: URL. This is wrong, but not
terribly important since file: URLs are inevitably system-specific.)

Comment 6

[Andreas Otte]

There is still some conversion stuff in nsURLHelper. See bug 32895 for more
information.