Created attachment 398439 [details] HTML script element-initiated request with 404 response (comparing Firefox, Safari, Chrome, and Edge) This is equivalent to the following Chrome bug: https://bugs.chromium.org/p/chromium/issues/detail?id=883400 Steps to reproduce the problem: 1. Load a page that requests a script that responds with a status code of 404. 2. Open Console in Developer Tools 3. Enter "var urls = []; window.performance.getEntriesByType('resource').forEach(function(r){urls.push(r.name)});" 4. The URL returning the 404 will not be displayed in the list of URLs What is the expected behavior? The URL returning the 404 should be displayed in the list of URLs. See the attached screenshots to see how Safari treats 404s from different request initiator types. Firefox is the only browser that implements this correctly.
Created attachment 398440 [details] HTML img element-initiated request with 404 response (comparing Firefox, Safari, Chrome, and Edge) This screenshot shows how Safari correctly includes 404 responses from <img> elements, but not <script> elements.
<rdar://problem/62947219>
A Chrome engineer has submitted a patch for the corresponding Chrome bug: https://bugs.chromium.org/p/chromium/issues/detail?id=883400#c28 This may be useful for the WebKit fix.
This is actually: <rdar://44388482>