- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Fri, 15 Jun 2012 15:57:35 +0200
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Adam Barth <w3c@adambarth.com>, Michael™ Smith <mike@w3.org>, www-archive <www-archive@w3.org>
On Fri, Jun 15, 2012 at 3:49 PM, Julian Reschke <julian.reschke@gmx.de> wrote: > That discussion went nowhere, as far as I recall. In particular it was > claimed that something webkit does is needed for web compatibility but then > we heard that mozilla disagreed (I think it was the special treatment of "\" > outside file: URIs). That was by far not all of it. > What would be helpful is a clear problem statement. Like "the RFCs force us > to handle this URI in a way that is incompatible with existing content". I'm > sure there *are* problems, but simply writing down what webkit happens to do > today (*) makes it incredibly hard to see what the difference is. I gave you an example already. Something that came up recently at Opera is whether a raw "\" in the query component needs to be escaped. More than two slashes following an hierarchical scheme is another. As I and others explained before, the RFCs leave a lot up to implementations and that does not match what we need. We could try to write something on top of those RFCs, but so far nobody has been successful at that. -- Anne — Opera Software http://annevankesteren.nl/ http://www.opera.com/
Received on Friday, 15 June 2012 13:58:04 UTC