W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2014

Re: [whatwg] URL interop status and reference implementation demos

From: Domenic Denicola <d@domenic.me>
Date: Wed, 19 Nov 2014 14:55:21 +0000
To: Sam Ruby <rubys@intertwingly.net>
Message-ID: <276bf816708349f4b93d94b2c8a9d87e@CY1PR0501MB1369.namprd05.prod.outlook.com>
Cc: whatWG <whatwg@whatwg.org>
From: Sam Ruby [mailto:rubys@intertwingly.net] 

> These results compare user agents against each other.  The testdata is provided for reference.

Then why is testdata listed as a user agent?

> I am not of the opinion that the testdata should be treated as anything other than as a proposal at this point.  Or to put it another way, if browser behavior is converging to something other than what than what the spec says, then perhaps it is the spec that should change.

Sure. But I was hoping to see a list of user agents that differed from the test data, so we could target the problematic cases. As is I'm not sure how to interpret a row that reads "user agents with differences: testdata chrome firefox ie" versus one that reads "user agents with differences: ie safari".

> web-platform-tests is huge.  I only need a small piece.  So for now, I'm making do with a "wget" in my Makefile, and two patch files which cover material that hasn't yet made it upstream.

Right, I was suggesting the other way around: hosting the evolving-along-with-the-standard testdata.txt inside whatwg/url, and letting web-platform-tests pull that in (with e.g. a submodule).
Received on Wednesday, 19 November 2014 14:55:52 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:26 UTC