RE: [agenda] Web Performance WG Teleconference #28 Agenda 2011-04-13

We have submitted an additional test case as well, for:
* In case of a page reload, all timing attributes should return values corresponding to the new navigation.

Here is the new submitted test:
http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTiming/test_timing_reload.htm

- Nic

From: Zhiheng Wang [mailto:zhihengw@google.com]
Sent: Wednesday, April 13, 2011 11:09 AM
To: Nic Jansma
Cc: public-web-perf@w3.org
Subject: Re: [agenda] Web Performance WG Teleconference #28 Agenda 2011-04-13

  In terms of the next set of testing cases, here are a couple suggestions:

* If the transport connection fails and the user agent reopens a connection, connectStart and connectEnd should return the corresponding values of the new connection.

* Some user agents maintain the DOM structure of the document in memory during navigation operations such as forward and backward. In those cases, the window.performance.timing and window.performance.navigation objects must not be altered during the navigation.

* In case of a page reload, all timing attributes should return values corresponding to the new navigation.

* In case when a persistent connection is used, domainLookupStart/End and connectStart/End should equal to fetchStart

* When document is retrieved from the application cache, domainLookupStart/End and connectStart/End should equal to fetchStart

* If there is no previous document, navigationStart must return the same value as fetchStart. unloadEventStart/End must return 0.

cheers,
Zhiheng


On Tue, Apr 12, 2011 at 3:21 PM, Nic Jansma <Nic.Jansma@microsoft.com<mailto:Nic.Jansma@microsoft.com>> wrote:
Below is the proposed agenda for Wednesday's meeting. Please reply with additional topics.

Zakim Bridge Numbers:
+1.617.761.6200<tel:%2B1.617.761.6200>, +33.4.26.46.79.03<tel:%2B33.4.26.46.79.03> and +44.203.318.0479<tel:%2B44.203.318.0479>.
Passcode 97373 (WPERF)

IRC channel #webperf on irc.w3.org:6665<http://irc.w3.org:6665>   http://irc.w3.org/
Teleconference Time and Length (60min): 3-4PM EST/1-2PM PST


1.       NavigationTiming Test updates

2.       NavigationTiming navigationStart in cross-origin redirected navigations

3.       NavigationTiming wall-clock time

4.       Feedback on 4/5 updates to Resource Timing

5.       Feedback on Unified Timing Proposal

6.       Discussion on User Timing

7.       Any other business

Thanks,
Nic