Re: [whatwg/fetch] Add more timing iformation about (interim) responses (PR #1483)

@annevk commented on this pull request.

To confirm, all these times are only exposed for CORS-same-origin resources?

> @@ -5528,22 +5531,32 @@ optional boolean <var>forceNewConnection</var> (default false), run these steps:
       <p>While true:
 
       <ol>
-       <li><p>If <var>timingInfo</var>'s
-       <a for="fetch timing info">final network-response start time</a> is 0, then set
-       <var>timingInfo</var>'s <a for="fetch timing info">final network-response start time</a> to
+       <li><p>Set <var>timingInfo</var>'s
+       <a for="fetch timing info">final network-response start time</a> to the

So this will change for each response currently delivered with preceding 1xx responses, right? Does it not matter because this is not exposed CORS-cross-origin?

>   <dt><dfn export for="fetch timing info">final network-response start time</dfn> (default 0)
+ <dt><dfn export for="fetch timing info">final network-response headers end time</dfn> (default 0)
+ <dt><dfn export for="fetch timing info">response body start time</dfn> (default 0)

This should have the "final network-" prefix.

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

Message ID: <whatwg/fetch/pull/1483/review/1120105655@github.com>