W3C home > Mailing lists > Public > public-web-perf@w3.org > November 2012

Proposed new test for Navigation Timing: Monolitic Clock

From: Philippe Le Hegaret <plh@w3.org>
Date: Fri, 30 Nov 2012 13:32:53 -0500
To: public-web-perf <public-web-perf@w3.org>
Message-ID: <1354300373.13984.600.camel@chacal>
Noticing some differences in implementations, I wrote a new simple test
for Navigation Timing:

http://w3c-test.org/webperf/tests/submission/W3C/NavigationTiming/monolitic.html

Firefox fails on it: the difference between domainLookupStart and
fetchStart is negative.

IE fails on the difference between domLoading and responseEnd since it
doesn't support document.readyState == "loading".

I'd appreciate if someone can look at the test and confirm that it is
correct.

I don't propose that we block on the test btw, ie it shouldn't get in
the way of moving the spec forward imho, but it would still be good to
add this test to our set.

I updated the implementation report to include the idlharness.js
results:
 http://www.w3.org/2012/04/navigation_timing_cr_results.html

Philippe
Received on Friday, 30 November 2012 18:33:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 30 November 2012 18:33:01 GMT