- From: Erik van der Poel <erikv@google.com>
- Date: Thu, 24 Dec 2009 16:22:26 -0800
- To: Mark Nottingham <mnot@mnot.net>
- Cc: Shawn Steele <shawn.steele@microsoft.com>, Gervase Markham <gerv@mozilla.org>, Simon Montagu <smontagu@smontagu.org>, Maciej Stachowiak <mjs@apple.com>, brettw@chromium.org, jshin@chromium.org, Anne van Kesteren <annevk@opera.com>, public-iri@w3.org, Shaopeng Jia <shaopengjia@google.com>
Hi Mark, Thanks for the email. Yes, the yellow highlights indicate test cases where the implementations give different results. I'm not sure I understand your question about <img> tags and HTML forms, but here are results for the latest versions of the implementations while running the <img> tests for the ?query part: http://curlies.googlecode.com/svn/trunk/test_results/latest/query_ascii_results.html And here are the corresponding results for HTML forms (which also use the ?query part): http://curlies.googlecode.com/svn/trunk/test_results/latest/form_get_ascii_results.html As you can see, for <img> tags with a ?query part, the implementations escape Space as %20, but for HTML forms they escape Space as +. Is this what you were asking about? We started with <a> tags, but that was very manual, so we switched to <img> tags, which are automated. We may try to find ways to test <a> tags in the future. Erik On Tue, Dec 22, 2009 at 4:08 PM, Mark Nottingham <mnot@mnot.net> wrote: > This is really cool. > > I'm assuming that the yellow highlights indicate cases where implementations differ, correct? > > AIUI you're testing both IMG tags and HTML forms, but I only see one set of results for each browser/os/test case combination. Did you not see any differentiation? > > Also, what about A tags and other means of generating links? > > Cheers, > > P.S. in the design document under "Test page generation", you have an unescaped <img> tag. > > > On 26/11/2009, at 6:49 AM, Erik van der Poel wrote: > >> We are happy to announce the open source release of Client URL >> Internet Emission Sniffer (CURLIES). >> >> The purpose of this project is to see how browsers and other Web >> clients transform URLs as they access them. This is done by generating >> a number of test cases and having each client load the test files >> while running a packet sniffer to capture the network emissions. >> Reports are then generated from the sniffed packets, highlighting >> differences between the clients. For further details and test results, >> see the project site: >> >> http://code.google.com/p/curlies/ >> http://code.google.com/p/curlies/wiki/DesignDocumentForClientURLInternetEmissionSniffer >> >> I have also written some recommendations for browser developers. While >> the HTML5 Web Addresses spec already describes how to parse and >> resolve a URL, I have taken this a step further to include the DOM >> interfaces that can be used to obtain IRIs, URIs and Unicode host >> names. >> >> http://code.google.com/p/curlies/wiki/RecommendationsForBrowserDevelopers >> http://www.w3.org/html/wg/href/draft >> >> Happy Thanksgiving! >> >> Erik >> >> PS Many thanks to Shaopeng Jia (Google), who did most of the actual work. >> > > > -- > Mark Nottingham http://www.mnot.net/ > >
Received on Friday, 25 December 2009 00:22:58 UTC