193902 2019-01-28 04:36:37 -0800 [Resource Timing] Should surface entries for failed requests (DNS, TCP, SSL, 4xx, 5xx) 2021-09-26 02:20:46 -0700 1 1 1 Unclassified WebKit WebCore Misc. Safari 12 All All REOPENED P2 Normal --- 1 nic webkit-unassigned achristensen noam oldest_to_newest 1498982 0 nic 2019-01-28 04:36:37 -0800 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. 1758980 1 achristensen 2021-05-11 11:03:14 -0700 *** This bug has been marked as a duplicate of bug 202040 *** 1759533 2 nic 2021-05-12 21:06:08 -0700 @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! 1759702 3 achristensen 2021-05-13 09:00:13 -0700 Reopening then 1764418 4 achristensen 2021-05-27 11:09:38 -0700 See https://github.com/whatwg/fetch/issues/1215 1797285 5 noam 2021-09-26 02:20:46 -0700 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