Re: parsing URI (references) according to RFC 3986

On Sun, Jun 19, 2011 at 8:56 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> 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.

Would you be interested in treating \ and / equivalently in more
schemes in order to converge behavior with IE, Chrome, and Safari?

Adam

Received on Monday, 20 June 2011 04:04:21 UTC