W3C home > Mailing lists > Public > public-web-perf@w3.org > March 2011

RE: test_timing_attributes_order.htm

From: Nic Jansma <Nic.Jansma@microsoft.com>
Date: Tue, 29 Mar 2011 23:54:00 +0000
To: Nic Jansma <Nic.Jansma@microsoft.com>, James Simonsen <simonjam@chromium.org>, public-web-perf <public-web-perf@w3.org>
Message-ID: <F677C405AAD11B45963EEAE5202813BD19CCB7C0@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
We have updated this test per your feedback.

- Nic

From: public-web-perf-request@w3.org [mailto:public-web-perf-request@w3.org] On Behalf Of Nic Jansma
Sent: Tuesday, March 22, 2011 4:29 PM
To: James Simonsen; public-web-perf
Subject: RE: test_timing_attributes_order.htm

Thanks James, we agree with your comments.  We'll get this test updated shortly.

- Nic

From: public-web-perf-request@w3.org [mailto:public-web-perf-request@w3.org] On Behalf Of James Simonsen
Sent: Wednesday, March 16, 2011 6:03 PM
To: public-web-perf
Subject: Re: test_timing_attributes_order.htm

On Wed, Mar 9, 2011 at 5:30 PM, Nic Jansma <Nic.Jansma@microsoft.com<mailto:Nic.Jansma@microsoft.com>> wrote:
We submitted our updated test_timing_attributes_order test today for consideration:
                http://test.w3.org/webperf/tests/submission/Microsoft/NavigationTiming/test_timing_attributes_order.htm

Thanks for the new test. It looks good, but with two suggestions:

test_timing_order('domLoading', 'fetchStart');  // instead of responseEnd

DOM loading should occur when the document is created. That's likely to happen before we've seen the full response.

test_timing_order('domInteractive', 'responseEnd');  // instead of domLoading
Interactive should occur once we've finished parsing. The end of the response should be closer to this than domLoading.

James
Received on Tuesday, 29 March 2011 23:54:34 UTC

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