Re: [whatwg/fetch] Expose PerformanceResourceTiming in Response Objects (#491)

The problem does sound more generic than just `fetch()`, indeed. The way browsers manage this is that each global has a "fetch group" (defined with not sufficient detail in Fetch today) that tracks all the ongoing fetches. It's a little more complicated than that as fetch groups can sometimes cross globals, but that's the basics. If we had that kind of thing and also a way to represent ongoing fetches through `fetch()` (which we're working on for the termination API), we could link them together more easily and you could find one from the other. And then we could do the same for elements, etc.

-- 
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/491#issuecomment-280857898