- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Sun, 19 Jun 2011 23:56:09 -0400
- To: public-iri@w3.org
On 6/19/11 8:10 PM, Adam Barth wrote: > Indeed. The point is that IE, Chrome, and Safari treat \ as if it > were / in parsing URLs whereas Firefox does not. I suspect we'll want > the spec to say that \ should be treated like / when parsing URLs. As a note, Gecko treats \ as / in when parsing URIs with the scheme "file" in builds compiled for Windows and OS2. We don't do that in any other circumstances. -Boris P.S. In Gecko's case, also on Windows and OS2, for urls that parse like "file" (ones where we don't expect an authority section), there's some sort of magic to detect that things like "file://c:/foo" or "file://c|/foo" is actually to be parsed as something with host = "" and file path "/c|/foo" as opposed to something with host "c:" or "c|". I have no idea whether other UAs do something similar...
Received on Monday, 20 June 2011 03:56:37 UTC