Re: [whatwg/fetch] Initial resource timing integration. (#1185)

@noamr commented on this pull request.



> +  <dt><dfn for="fetch timing info">connection timing info</dfn> (default null)
+  <dd>A <a for=/>connection timing info</a>.
+</dl>
+
+<p>A <dfn>connection timing info</dfn> is a <a for=/>struct</a> used to maintain timing information
+pertaining to the process of obtaining a connection. It has the following <a for=struct>items</a>:
+<dl>
+  <dt><dfn for="connection timing info">domain lookup start time</dfn> (default zero)
+  <dd>A <a for=/>DOMHighResTimeStamp</a>
+  <dt><dfn for="connection timing info">domain lookup end time</dfn> (default zero)
+  <dd>A <a for=/>DOMHighResTimeStamp</a>
+  <dt><dfn for="connection timing info">connection start time</dfn> (default zero)
+  <dd>A <a for=/>DOMHighResTimeStamp</a>
+  <dt><dfn for="connection timing info">connection end time</dfn> (default zero)
+  <dd>A <a for=/>DOMHighResTimeStamp</a>
+  <dt><dfn for="connection timing info">secure connection start time</dfn> (default zero)

But the RT spec explicitly says that `connectEnd` should occur after the TLS handshake started... https://w3c.github.io/resource-timing/#dom-performanceresourcetiming-connectend: 

"The returned time MUST include the time interval to establish the transport connection, as well as other time intervals such as SOCKS authentication. It MUST include the time interval to complete enough of the TLS handshake to request the resource"

So I think it's actually `connectStart <= secureConnectionStart <= connectEnd` if to judge by current spec.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1185#discussion_r587508575