This is a request for an un-do of https://bugs.webkit.org/show_bug.cgi?id=104762 Per the latest ResourceTiming (Level 2) spec: https://www.w3.org/TR/resource-timing-2/#resources-included-in-the-performanceresourcetiming-interface > If a resource fetch was aborted due to a networking error (e.g. DNS, TCP, or TLS error), then the fetch MAY be included as a PerformanceResourceTiming object in the Performance Timeline with initialized attribute values up to the point of failure - e.g. a TCP handshake error should report DNS timestamps for the request, and so on. While the language says MAY, I'm requesting that failed entries (transport-level and HTTP 4xx/5xx) be included in ResourceTiming in Safari.
*** This bug has been marked as a duplicate of bug 202040 ***
@Alex this isn't fully addressed though, transport-level errors (DNS/TCP/SSL) still don't surface a ResourceTiming entry. Test case at: https://nicj.net/dev/resourcetiming/error-resources.html The 4xx and 5xx cases work now thanks!
Reopening then
See https://github.com/whatwg/fetch/issues/1215
I'm currently editing the spec to explicitly create resource timing entries for network errors. Track https://github.com/whatwg/fetch/pull/1311 for spec work Track https://github.com/web-platform-tests/wpt/issues/30968 for tests