Re: [whatwg/fetch] Attach timing info and URL to network errors, and report for fetch API (#1311)

> Looking...
> 
> I don't have a plan to implement this to Chrome at this moment. @npm1 @yoavweiss do you?

@yutakahirano 
Reminding of the context of a discussion we've had in the WebPerfWG about this some months ago: https://github.com/whatwg/fetch/issues/1215

There is currently an issue that IMO needs to be addressed, where we ResourceTiming entries are created for CORS-fail responses, but not for other network errors. This allows the caller to know whether he was cors-rejected or had a different error like a timeout - information which the caller should generally shouldn't have.
 
The direction the WG aligned on was creating RT entries for all network errors, so that that information is not lost but not distinguishable.

Hope the context is clearer :)

-- 
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/pull/1311#issuecomment-953505935