Re: [whatwg/fetch] When response comes from a worker, some of the timing-info should pass through (#1208)

OK the problem here is that in the case of service workers, there could be *two fetches* with *one response*. One fetch is the original fetch from the document, and the other one is the potential `fetch()` call inside the service worker.

The timing info of the internal fetch is available in the performance timeline of the service worker itself.

It should probably be clearer in the spec, that when a response comes from a service worker, it's something like a clone of the response, or some similar construct, and that attaching the timing info to the response is only applicable for this instance of fetch, i.e., attaching `fetch timing info` to the response in the document fetch does not alter the `fetch timing info` accessible from within the service worker.

Perhaps also a test to that effect could clarify things.


-- 
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/issues/1208#issuecomment-940153231