Re: [whatwg/fetch] Update HTTPFetch algorithm to support new SW Handle Fetch returns (PR #1832)

@yoshisatoyanagisawa commented on this pull request.



>  
-    <ol>
-     <li><p>Set <var>fetchParams</var>'s <a for="fetch params">timing info</a>'s
-     <a for="fetch timing info">final service worker start time</a> to
-     <var>serviceWorkerStartTime</var>.
+    <p>If <var>fetchResponse</var> is non-null, then:
+     <ol>
+     <li><p>If<var>fetchResponse</var> is <a for=/>response</a>, then:
+      <ol>
+       <li><p>Set <var>response</var> to <var>fetchResponse</var>.
+       <li><p>Set <var>fetchParams</var>'s <a for="fetch params">timing info</a>'s
+       <a for="fetch timing info">final service worker start time</a> to
+       <var>serviceWorkerStartTime</var>.
+       <li><p>Set <var>fetchParams</var>'s <a for="fetch params">timing info</a>'s

It is not a blocker but resource-timing may not not have a trivial way to know `response`, right?  I just wondered why we need to copy the timing info.

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

Message ID: <whatwg/fetch/pull/1832/review/2960634012@github.com>