- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 03 Nov 2011 19:44:19 +0100
- To: Jeni Tennison <jeni@jenitennison.com>
- CC: "www-tag@w3.org List" <www-tag@w3.org>
On 2011-11-03 19:22, Jeni Tennison wrote: > Julian, > > (I wasn't ignoring what you wrote, just wanted to check it out, hence the delay :) > > On 2 Nov 2011, at 15:11, Julian Reschke wrote: >> 2) "\" and "/": >> >> 2a) The uniform treatment of "\" hasn't agreement; for instance, Firefox does it only for file URIs (as far as I recall). >> >> 2b) That being said, "\" doesn't appear in syntactically valid URIs or IRIs anyway, so maybe we can ignore the question; it won't affect any valid URI/IRI anyway. > > > That being the case, how would any URL that contained a "\" get to step 12 of the HTML5 resolution algorithm [1] where they're swapped for "/"s given that step 10 says (I think!) that syntactically invalid URI/IRIs will raise an error and stop the resolution? > ... That appears to be a bug (or a feature, depending on p.o.v.). It's good that more people start to pay attention :-) Best regards, Julian
Received on Thursday, 3 November 2011 18:45:00 UTC