From a18e4e39001a9c6b165a41fa50162b1b7dfaf6cf Mon Sep 17 00:00:00 2001
From: Noam Rosenthal <noamr@users.noreply.github.com>
Date: Fri, 2 Sep 2022 09:14:23 +0300
Subject: [PATCH] Add more timing iformation about (interim) responses

See https://github.com/w3c/resource-timing/issues/345

Since early hints have landed, there are additional useful timestamps
that are currently not exposed:

- First interim response start (e.g. when we received a 103)
  as a different timestamp from the final response start
  (e.g. when we received the 200)

- Final headers received (when the last header has been received and
  we're ready for the body)

- First bytes of the body received

The naming in #345 is not finalized yet, but it's clear that these
are the 3 interesting timestamps. This PR exposes those for later
use by resource timing.
---
 fetch.bs | 28 +++++++++++++++++++++++++---
 1 file changed, 25 insertions(+), 3 deletions(-)

diff --git a/fetch.bs b/fetch.bs
index eca7c7dbb..b85cfa893 100644
--- a/fetch.bs
+++ b/fetch.bs
@@ -342,7 +342,10 @@ following <a for=struct>items</a>: [[RESOURCE-TIMING]] [[NAVIGATION-TIMING]]
  <dt><dfn export for="fetch timing info">post-redirect start time</dfn> (default 0)
  <dt><dfn export for="fetch timing info">final service worker start time</dfn> (default 0)
  <dt><dfn export for="fetch timing info">final network-request start time</dfn> (default 0)
+ <dt><dfn export for="fetch timing info">first interim network-response start time</dfn> (default 0)
  <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)
  <dt><dfn export for="fetch timing info">end time</dfn> (default 0)
  <dd>A {{DOMHighResTimeStamp}}.
 
@@ -5994,9 +5997,8 @@ 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
        <a for=/>coarsened shared current time</a> given <var>fetchParams</var>'s
        <a for="fetch params">cross-origin isolated capability</a>, immediately after the user
        agent's HTTP parser receives the first byte of the response (e.g., frame header bytes for
@@ -6004,6 +6006,11 @@ optional boolean <var>forceNewConnection</var> (default false), run these steps:
 
        <li><p>Wait until all the HTTP response headers are transmitted.
 
+       <li><p>Set <var>timingInfo</var>'s
+       <a for="fetch timing info">final network-response headers end time</a> to
+       <a for=/>coarsened shared current time</a> given <var>fetchParams</var>'s
+       <a for="fetch params">cross-origin isolated capability</a>.
+
        <li><p>Let <var>status</var> be the HTTP response's status code.
 
        <li>
@@ -6017,6 +6024,14 @@ optional boolean <var>forceNewConnection</var> (default false), run these steps:
          <li><p>If <var>request</var>'s <a for=request>mode</a> is "<code>websocket</code>" and
          <var>status</var> is 101, then <a for=iteration>break</a>.
 
+         <li><p>If <var>timingInfo</var>'s
+         <a for="fetch timing info">first interim network-response start time</a> is 0, then set
+         <var>timingInfo</var>'s
+         <a for="fetch timing info">first interim network-response start time</a> to
+         <var>timingInfo</var>'s <a for="fetch timing info">final network-response start time</a>.
+
+         <li><p>If <var>status</var> is 101, <a for=iteration>break</a>.
+
          <li><p>If <var>status</var> is 103 and <var>fetchParams</var>'s
          <a for="fetch params">process early hints response</a> is non-null, then
          <a>queue a fetch task</a> to run <var>fetchParams</var>'s
@@ -6197,6 +6212,13 @@ optional boolean <var>forceNewConnection</var> (default false), run these steps:
         <p>If one or more bytes have been transmitted from <var>response</var>'s message body, then:
 
         <ol>
+         <li><p>If <var>fetchParams</var>'s <a for="fetch params">timing info</a>'s
+         <a for="fetch timing info">response body start time</a> is 0, then set
+         <var>fetchParams</var>'s <a for="fetch params">timing info</a>'s
+         <a for="fetch timing info">response body start time</a> to the
+         <a for=/>coarsened shared current time</a> given <var>fetchParams</var>'s
+         <a for="fetch params">cross-origin isolated capability</a>.
+
          <li><p>Let <var>bytes</var> be the transmitted bytes.
 
          <li><p>Let <var>codings</var> be the result of <a>extracting header list values</a> given