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

Not being able to distinguish which resource timing entry corresponds to which fetch seems like a legitimate shortcoming of resource timing API. 
Your proposal sounds quite interesting and plausible, it does break away significantly from the performance timing model but would open up a lot of new possibilities. This requires more thought and discussion as this is not just about fetch, but making performance entires available via other platform API interfaces (in general).
I'd move the issue to Performance timing repo, as this is not specific to fetch as I see it.

-- 
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-280798862

Received on Friday, 17 February 2017 23:56:28 UTC