W3C home > Mailing lists > Public > public-html@w3.org > February 2010

Re: testing URL decomposition (related to ISSUE-56)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 11 Feb 2010 15:26:05 +0100
Message-ID: <4B74137D.7030801@gmx.de>
To: Maciej Stachowiak <mjs@apple.com>
CC: Aryeh Gregor <Simetrical+w3c@gmail.com>, "public-html@w3.org" <public-html@w3.org>
Maciej Stachowiak wrote:
> Of the browsers I tried (Firefox, Opera, Safari, Chrome), Firefox had 
> the most green and I don't see any problem with changing Safari to match.

OK, should the spec also match Firefox then?

> There is one behavior checked by these tests that seem potentially 
> unwise: trying to differentiate between URLs that had particular 
> percent-escaping in the original source vs. equivalent ones that did 
> not. All browsers I tried seem to either consistently escape or 
> consistently unescape in any given component. Unless IE differentiates I 
> don't think we can conclude that this is required behavior.

Actually, IE *does* differentiate, so the pathname components returned for

   http://example.org/a-umlaut-

and

   http://example.org/a-umlaut-%C3%A4

are different.

Anyway, what this shows is that implementing the algorithm for the URL 
decomposition IDL attributes according to WEBADDRESSES is *not* required 
for compatibility with existing content -- maybe because it's simply not 
used a lot for broken URIs, or because the differences do not matter in 
practice, or because code has learned to work around them (such as by 
inserting "/" when pathname doesn't return a leading "/").

Now what will be much more interesting is to find out whether the rules 
in WEBADDRESSES are actually used for navigation, but that'll require 
different test cases.

Best regards, Julian
Received on Thursday, 11 February 2010 14:26:47 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:14 UTC