- From: Karen Anderson (IE) <Karen.Anderson@microsoft.com>
- Date: Fri, 11 May 2012 16:39:14 +0000
- To: Tony Gentilcore <tonyg@google.com>
- CC: "public-web-perf@w3.org" <public-web-perf@w3.org>
Received on Friday, 11 May 2012 16:40:43 UTC
That sounds like a nice value-add. I can work on that for next week. Thanks, Karen From: Tony Gentilcore [mailto:tonyg@google.com] Sent: Monday, May 07, 2012 6:50 PM To: Karen Anderson (IE) Cc: public-web-perf@w3.org Subject: Re: Action 99: Update test_timing_attributes_order test and document_readiness_exists investigations Hi Karen, Thanks for the updates. 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 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 Friday, 11 May 2012 16:40:43 UTC