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

Re: Action 99: Update test_timing_attributes_order test and document_readiness_exists investigations

From: Tony Gentilcore <tonyg@google.com>
Date: Mon, 7 May 2012 18:50:06 -0700
Message-ID: <CANvLf_GEicfiUY9he-m+_oddJVcX=ghyLFOrbfsC_qcqZG3dWg@mail.gmail.com>
To: "Karen Anderson (IE)" <Karen.Anderson@microsoft.com>
Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>
Hi Karen, Thanks for the updates.

*
> http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTiming/test_timing_attributes_order.htm
> *<http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTiming/test_timing_attributes_order.htm>
>

Looks good to me.


> *
> http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTiming/test_document_readiness_exist.html
> *<http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTiming/test_document_readiness_exist.html>
>

This test checks that document.readyState has the right value at the right
time. That's fine, but isn't related to Navigation Timing. To make it
relevant, we should verify that each of
performance.timing.{domLoading,domInteractive,domComplete} are 0 prior to
reaching each readiness phase and are >0 after reaching it.

-Tony
Received on Tuesday, 8 May 2012 01:51:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:32 UTC