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

RE: [NavigationTiming] Redirect test cases

From: Nic Jansma <Nic.Jansma@microsoft.com>
Date: Mon, 25 Apr 2011 18:56:38 +0000
To: Tony Gentilcore <tonyg@google.com>
CC: "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <F677C405AAD11B45963EEAE5202813BD19D453F5@TK5EX14MBXW652.wingroup.windeploy.ntdev.microsoft.com>
I've made two updates to test_timing_xserver_redirect:
	http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTiming/test_timing_xserver_redirect.htm

1) navigationStart is validated to be >0 for cross-origin redirected navigations per last weeks' spec update
2) The starting origin (w3c-test.org) and redirected origin (www.w3c-test.org) are set as variables and validated before the test starts.

IE9 and Chrome currently fail because of change #1 above.

- Nic

-----Original Message-----
From: Tony Gentilcore [mailto:tonyg@google.com] 
Sent: Wednesday, March 30, 2011 1:05 PM
To: Nic Jansma
Cc: public-web-perf@w3.org
Subject: Re: [NavigationTiming] Redirect test cases

With the exception of the change you noted below, the new tests both look good to me.

On Wed, Mar 30, 2011 at 12:44 PM, Nic Jansma <Nic.Jansma@microsoft.com> wrote:
> We noticed that for the cross-server redirection test case, we're 
> incorrectly testing that redirectCount should be 1:
>
>
> http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTimin
> g/test_timing_xserver_redirect.htm
>
>
>
> Per the spec, it should be 0 for cross-origin redirects.
>
> https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Ove
> rview.html#nt-navigation-info-redirect-count
>
>
>
> We will update the test.
>
>
>
> - Nic
>
>
>
> From: public-web-perf-request@w3.org 
> [mailto:public-web-perf-request@w3.org]
> On Behalf Of Nic Jansma
> Sent: Wednesday, March 30, 2011 11:44 AM
> To: public-web-perf@w3.org
> Subject: [NavigationTiming] Redirect test cases
>
>
>
> Hi everyone,
>
>
>
> We've submitted two new test cases for NavigationTiming.  These tests 
> look at the behavior of redirectCount, redirectStart and redirectEnd 
> for navigations that contain a server-side redirect (via an IFRAME).
>
>
>
> This test looks at same-origin redirected navigations:
>
> http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTimin
> g/test_timing_server_redirect.htm
>
>
>
> This test looks at cross-origin redirected navigations:
>
> http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTimin
> g/test_timing_xserver_redirect.htm
>
>
>
> Both tests utilize a redirect.php, which is a modified version from 
> the XMLHttpRequest/resources/ directory.  We figured it would be 
> better to include a version in our own resources/ directory than 
> depend on a non-shared resources directory under webapps/.
>
>
>
> The tests need to be started from w3c-test.org for the cross-origin 
> navigation case, as it redirects initially to www.w3c-test.org.  Is 
> there a good way to enforce this requirement?
>
>
>
> We just submitted these today so we are asking for feedback over the 
> next week to be able to be discussed at the 4/6 conference call.
>
>
>
> Thanks,
>
>
>
> - Nic
Received on Monday, 25 April 2011 18:57:09 UTC

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