An event handler for the error
event. Error events are fired at various targets for different kinds of errors:
- When a JavaScript runtime error (including syntax errors) occurs, an
error
event using interfaceErrorEvent
is fired atwindow
andwindow.onerror()
is invoked. - When a resource (such as an
<img>
or<script>
) fails to load, anerror
event using interfaceEvent
is fired at the element, that initiated the load, and theonerror()
handler on the element is invoked. These error events do not bubble up to window, but (at least in Firefox) can be handled with a single capturingwindow.addEventListener
.
Installing a global error
event handler is useful for automated collection of error reports.
Syntax
For historical reasons, different arguments are passed to window.onerror
and element.onerror
handlers.
window.onerror
window.onerror = function(message, source, lineno, colno, error) { ... }
Function parameters:
message
: error message (string). Available asevent
(sic!) in HTMLonerror=""
handler.source
: URL of the script where the error was raised (string)lineno
: Line number where error was raised (number)colno
: Column number for the line where the error occurred (number)error
: Error Object (object)
When the function returns true
, this prevents the firing of the default event handler.
element.onerror
element.onerror = function(event) { ... }
element.onerror
accepts a function with a single argument of type Event
.
Notes
When a syntax(?) error occurs in a script, loaded from a different origin, the details of the syntax error are not reported to prevent leaking information (see bug 363897). Instead the error reported is simply "Script error."
This behavior can be overriden in some browsers using the
attribute on crossorigin
<script>
and having the server send the appropriate CORS HTTP response headers.
When using the inline HTML markup (<body onerror="alert('an error occurred')">
), the HTML specification requires arguments passed to onerror
to be named event
, source
, lineno
, colno
, error
. In browsers that have not implemented this requirement, they can still be obtained via arguments[0]
through arguments[2]
.
Specifications
Specification | Status | Comment |
---|---|---|
WHATWG HTML Living Standard The definition of 'onerror' in that specification. |
Living Standard |
Browser compatibility
Before Firefox 14 when a <script>
failed to load, window.onerror
was invoked with message "Error loading script". This was fixed in bug 737087, now scriptElement.onerror
is invoked instead in such cases.
Since Firefox 31, the last 2 arguments (colno
and error
) were added, meaning you can access the stack trace of a script error from window.onerror
via the provided Error
object (bug 355430.)