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

@yoavweiss 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)

Seems to me that it would be best to keep the "secure connection start time" value in Fetch, and add a TODO to test current implementations to see that they match the prose rather than the diagram. At least for Chromium, it seems like it's *supposed* to match the prose (i.e. `connectStart` <= `connectEnd` <= `secureConnectionStart`)

-- 
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_r587432037