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

@noamr commented on this pull request.



> +<ol>
+  <li>Let <var>globalObject</var> be <var>fetchParams</var>'s <a for="fetch params">request</a>'s
+  <a for=request>client</a>'s <a for="environment settings object">global object</a>.
+  <li>Let <var>timingInfo</var> be <var>fetchParams</var>'s <a for="fetch params">timing info</a>.
+  <li>Let <var>requestedURL</var> be <var>response</var>'s <a for=response>URL list</a>'s first item.
+  <li>If <var>response</var>'s <a for=response>timing allow passed flag</a> is not set, set
+  <var>timingInfo</var> to a new <a for=/>fetch timing info</a>, with its
+  <a for="fetch timing info">fetch start time</a> set to <var>timingInfo</var>'s
+  <a for="fetch timing info">fetch start time</a>,
+  <a for="fetch timing info">response end time</a> set to <var>timingInfo</var>'s
+  <a for="fetch timing info">response end time</a>,
+  <a for="fetch timing info">connection timing info</a> set to a new
+  <a for=/>connection timing info</a> with its
+  <a for="connection timing info">alpn negotiated protocol</a> set to <var>timingInfo</var>'s
+  <a for="fetch timing info">connection timing info</a>'s
+  <a for="connection timing info">alpn negotiated protocol</a>.

I agree. Ongoing discussion about this: https://github.com/w3c/resource-timing/pull/224
Trying to align fetch with resource-timing before making changes to the content.

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