Thanks James, great feedback. We've submitted an update for the three suggestions you mention below. http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTiming/test_timing_xserver_redirect.htm http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTiming/test_timing_server_redirect.htm - Nic From: public-web-perf-request@w3.org [mailto:public-web-perf-request@w3.org] On Behalf Of James Simonsen Sent: Thursday, April 07, 2011 1:38 PM To: public-web-perf@w3.org Subject: Re: [minutes] 20110406 Web Performance WG Teleconference #27 On Wed, Apr 6, 2011 at 2:10 PM, Jatinder Mann <jmann@microsoft.com<mailto:jmann@microsoft.com>> wrote: Summary of Action Items ACTION-18 - Follow up on test coverage and propose new test cases. [on Zhiheng Wang - due 2011-04-13]. I took a look at the new Navigation Timing tests that exercise redirects. Thanks for submitting them! I just wanted to make a couple of comments: http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTiming/test_timing_server_redirect.htm 1. We should verify that navigationStart is non-zero. If we accidentally zero it out thinking it's cross-server (or any other buggy reason), the rest of the tests won't detect it. 2. This is redundant and can be removed: test_timing_order('redirectEnd', 'navigationStart'); http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTiming/test_timing_xserver_redirect.htm 1. As of right now, this should also check that navigationStart is 0. JamesReceived on Wednesday, 13 April 2011 17:51:00 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 13 April 2011 17:51:01 GMT