W3C home > Mailing lists > Public > public-test-infra@w3.org > October to December 2011

[Bug 14839] Separate WebKit into Safari and Chrome

From: <bugzilla@jessica.w3.org>
Date: Wed, 23 Nov 2011 17:58:41 +0000
To: public-test-infra@w3.org
Message-Id: <E1RTH5l-0008FE-4e@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14839

--- Comment #2 from Tony Gentilcore <tonyg@chromium.org> 2011-11-23 17:58:40 UTC ---
(In reply to comment #1)
> Is this a report formatting issue or for these tests do you really consider
> Chrome and Safari to be independent implementations?

For navigation timing, half of the implementation is in WebKit. The other half
is in the browser's network stack which is implemented separately by each port
of WebKit. Currently Chrome has it implemented and thus the API is flipped on
in WebKit. Safari has not implemented that side so the API is disabled in
WebKit.

> In other words, if your CR exit criteria are two independent implementations,
> and the only passes you have are WebKit (Safari) and WebKit (Chrome), does that
> meet your exit criteria?

No. You are right, I didn't think of it that way. However, the converse is
equally concerning. If we had run the test more often in Safari than Chrome, it
would appear that we didn't have a conforming engine at all.

> Also, the intent of the current report is to show the status of meeting CR exit
> criteria. As all results are tracked by UA string, and engines are tracked
> independently of browsers, it would be easy to make a different report that
> shows results per browser and leave the current report alone.

I'd be in favor of a second report that separates out browsers. If for no other
reason than to feed bloggers and the like who enjoy quoting numbers like
"Browser X passes Y% of conformance tests."

However, that doesn't necessarily fully address the concern above.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 23 November 2011 17:58:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 23 November 2011 17:58:47 GMT