646214 - onerror is not called when a script fails to load on the file: protocol

Status: RESOLVED DUPLICATE of bug 621276

(Core :: DOM: Core & HTML, defect)

Description

[Erik Vold]

Steps to reproduce:

1. Download https://gist.github.com/893357#file_file_script.html some place on your hard drive.
2. open it

Expected Result:

An alert message that says "error"

Actual Result:

Nothing happens.

Comment 1

[(mostly gone) XtC4UaLL [:xtc4uall]]

Attachment: Reporter's Testcase

Comment 2

[(mostly gone) XtC4UaLL [:xtc4uall]]

Confirmed against Mozilla/5.0 (Windows NT 5.1; rv:2.2a1pre) Gecko/20110330 Firefox/4.2a1pre ID:20110330030437 back to 1.9.1.

On GC 12 loading the Testcase loacally fires the Error.
Opera 11 shows the same Behavior like Fx btw.

Comment 3

[Erik Vold]

IE seems to throw an error that can't be caught.
Webkit seems to do the expected behavior.
Gecko doesn't appear to do anything.

Comment 4

[Olli Pettay [:smaug][[e-mail]]]

Does Chrome fire error event even if the src points to a file in another directory?

Comment 5

[Olli Pettay [:smaug][[e-mail]]]

Although, that doesn't really matter, since it should never allow
loading such files. So firing error in those cases would be ok.

Comment 6

[Erik Vold]

> Does Chrome fire error event even if the src points to a file in another
directory?

I get the same results in all browsers if the file the src is pointing to is deep in a descendant folder. I haven't tried parent folder's or other directories.

Comment 7

[Boris Zbarsky [:bzbarsky]]

Probably a duplicate of one of the existing bugs on AsyncOpen throwing for file://