Open Bug 304959 Opened 21 years ago Updated 3 years ago

When an external script file fails to load a warning should be shown in the js console

Categories

(Core :: DOM: Core & HTML, enhancement, P5)

enhancement

Tracking

()

People

(Reporter: bugzilla.mozilla.org, Unassigned)

References

(Blocks 1 open bug)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.10) Gecko/20050717 Firefox/1.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.10) Gecko/20050717 Firefox/1.0.6 at present if an external script is requested with the wrong file path or filename it fails silently and an error only occurs when a function that should have been included is "not defined". In complicated scenarios this can be tricky to debug. What would be desirable is that a warning (or message - not sure what would be more appropriate) be raised in the console saying something like "External javascript file "http://www.yourdomain.tld/non-existant/file.js" could not be loaded" this would aid debugging immensly Reproducible: Always Steps to Reproduce: 1. create this file <html> <head> <title>Test Page</title> <script type="text/javascript" src="non-existant/file.js"></script> </head> <body> Blank </body> </html> 2.do NOT create non-existant/file.js 3.open page and look in the js console. Observe absence of any indication that the file has or has not loaded Actual Results: no indication that the file has or has not loaded Expected Results: had a message in the console for debugging purposes stating that the file failed to load.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Component: Error Console → DOM
Product: Firefox → Core
QA Contact: error.console → general
Blocks: 406489
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5
Component: DOM → DOM: Core & HTML
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.