W3C home > Mailing lists > Public > public-web-perf@w3.org > November 2010

[Navigation Timing] Feedback on the working draft

From: Anderson Quach <aquach@microsoft.com>
Date: Tue, 30 Nov 2010 02:32:52 +0000
To: "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <1E1FF4102DEA7A40AF9CC342044ECE5D2E302998@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
Section 1.0 Introduction

*         typo s/the time it take to/the time it takes to/

Section 4.2 The PerformanceTiming interface
unloadEventStart -

*         correction s/starts unloading<http://dev.w3.org/html5/spec/history.html#unloading-documents> the previous document/starts the unload event of the previous document/

unloadEventEnd -

*         correction s/finishes unloading<http://dev.w3.org/html5/spec/history.html#unload-a-document> the previous document/finishes the unload event of the previous document/

redirectStart -

*         typo, s/intiates/initiates/

*         correction s/the redirect and the document at the end of the redirect are from the same origin<http://dev.w3.org/html5/spec/origin-0.html#origin>/all the redirects or equivalent must come from the same origin/

*         removal, this text is confusing. If there is a redirectStart, this is captured immediately after navigationStart.  This nuance is better described in the processing model. - 'redirectStart is the equivalent of the fetchStart attribute of the navigation that initiates the redirect.'

redirectCount -

*         addition 'This attribute must be zero if there are any non-same origin redirects.'

redirectEnd -

*         removal, if there are different origins in the redirect chain then the redirectStart, redirectEnd and redirectCount must be zero. 'The relaxed same orgin policy doesn't provide sufficient protection against unauthorized visits across documents. In shared hosting, an untrusted third party is able to host an HTTP server at the same IP address but on a different port.'

domainLookupEnd -

*         typo s/immmediately/immediately/

connectEnd

*         To prevent undefined gaps in the timeline, it's recommended that the connectEnd time to be inclusive of SSL handshake and SOCKS authentication. The recommended text goes as follows: s/It must not include other time interval such as SSL handshake and SOCKS authentication/It can include other time interval such as SSL handshake and SOCKS authentication/

loadEventStart

*         typo s/the the/the/

Section 4.3 The PerformanceNavigation Interface
type -

*         typo s/url/URL/

Section 4.5 Processing Model
typo s/This secion/This section/

It should be sufficient to have one image that describes the Navigation timing timeline and express that the unload event can be on an independent timeline.

Step 13

*         Question: The wording of the comment in this step implies that the connection is then re-opened. Would you want it to state, the following instead: s/Return to step 11/Return to step 10/

*         Removal, this appears to be redundant as it's already covered in the processing model for initialization values of connectStart, connectEnd and requestStart. "When persistent connection [RFC 2616] is enabled, a user agent may first try to re-use an open connect to send the request while the connection can be asynchronously closed. In such case, connectStart, connectEnd and requestStart should represent timing information collected over the re-open connection."


________________________________
Received on Tuesday, 30 November 2010 02:34:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 21 December 2010 18:13:56 GMT