This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: https://html.spec.whatwg.org/multipage/workers.html Multipage: https://html.spec.whatwg.org/multipage/#importing-scripts-and-libraries Complete: https://html.spec.whatwg.org/#importing-scripts-and-libraries Referrer: https://html.spec.whatwg.org/multipage/ Comment: Ensure importScripts("http://... 404 error ...") is clearly defined Posted from: 91.182.51.213 by ms2ger@gmail.com User agent: Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0
http://www.w3c-test.org/workers/WorkerGlobalScope_importScripts_NetworkErr.htm tests for a NetworkError.
Checked in as WHATWG revision r8874. Check-in comment: Clarify what 'failed' means in importScripts(). https://html5.org/tools/web-apps-tracker?from=8873&to=8874
That's almost certainly not what's implemented though. HTTP 404 error is executed for scripts. Only actual network errors cause failure.
We should fix that for importScripts(), unless someone relies on it.
Why? What's the advantage? And what set of status codes should we accept instead post-redirect? 200-299?
The advantage is just to reduce the amount of script that gets executed when the author isn't expecting script to be executed. Just like honouring MIME types or magic signatures.
https://github.com/whatwg/html/pull/166