Bugzilla – Bug 15684
[URL] Replacing backslash with forward slash in URIs doesn't seem to be necessitated by web compat
Last modified: 2014-04-11 19:37:28 UTC
+++ This bug was initially created as a clone of Bug #12543 +++
Replacing backslash with forward slash in URIs doesn't seem to be necessitated
by web compat
Posted from: 126.96.36.199
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0a1) Gecko/20110422 Firefox/6.0a1
How do we know that?
(In reply to comment #1)
> How do we know that?
I think Boris already responded to that in bug 12543.
This is just a clone of that bug. I created this bug due to the HTML WG decision policy prohibiting the component of Last Call bugs from being changed.
To be clear though, going forward, I suggest that the discussion should take place here, and have suggested to HIxie that he move bug 12543 to resolved.
(In reply to comment #2)
> To be clear though, going forward, I suggest that the discussion should take
> place here, and have suggested to HIxie that he move bug 12543 to resolved.
IMHO the wrong thing to do until the HTML spec actually references that document.
One note: Chrome's behavior here causes problems for people trying to use backslash in URIs in at least some use cases. See http://stackoverflow.com/questions/10438008/different-behaviours-of-treating-backslash-in-the-url-by-firefox-and-chrome/10444621 for example.
As far as I can tell Gecko is the only browser that does not do this. I'd rather convince Gecko to change than everyone else. http://url.spec.whatwg.org/ handles / and \ identically in URLs with hierarchical schemes.
Just for the record: "Gecko doesn't do it" wasn't strictly true, after all. It did - but only on Windows for some odd reason..
Per https://bugzilla.mozilla.org/show_bug.cgi?id=652186 we've now officially surrendered anyway.
> It did - but only on Windows for some odd reason..
And only in the case when the backslashes came right after the ':' following the scheme, to be clear. And only for navigations, not all loads.
And it's Windows-only because it commonly came up only via users typing stuff in the URL bar on Windows.
> we've now officially surrendered anyway.
At least I have. It's just not worth it to me to spend any more time on this.