GlobalEventHandlers.onerror - Web APIs 编辑
The onerror
property of the GlobalEventHandlers
mixin is an EventHandler
that processes error
events.
Error events are fired at various targets for different kinds of errors:
- When a JavaScript runtime error (including syntax errors and exceptions thrown within handlers) occurs, an
error
event using interfaceErrorEvent
is fired atwindow
andwindow.onerror()
is invoked (as well as handlers attached bywindow.addEventListener
(not only capturing)). - 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 can be handled with awindow.addEventListener
configured withuseCapture
set totrue
.
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 (as well as on error-type window.addEventListener
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.
window.addEventListener('error')
window.addEventListener('error', function(event) { ... })
event
of type ErrorEvent
contains all the information about the event and the error.
element.onerror
element.onerror = function(event) { ... }
element.onerror
accepts a function with a single argument of type Event
.
A good example for this is when you are using an image tag, and need to specify a backup image in case the one you need is not available on the server for any reason.
<img src="imagenotfound.gif" onerror="this.onerror=null;this.src='imagefound.gif';" />
The reason we have the this.onerror=null
in the function is that the browser will be stuck in an endless loop if the onerror image itself generates an error.
Notes
When an error occurs in a script, loaded from a different origin, the details of the error are not reported to prevent leaking information (see bug 363897). Instead the error reported is "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. A workaround is to isolate "Script error." and handle it knowing that the error detail is only viewable in the browser console and not accessible via JavaScript.
window.onerror = function (msg, url, lineNo, columnNo, error) {
var string = msg.toLowerCase();
var substring = "script error";
if (string.indexOf(substring) > -1){
alert('Script Error: See Browser Console for Detail');
} else {
var message = [
'Message: ' + msg,
'URL: ' + url,
'Line: ' + lineNo,
'Column: ' + columnNo,
'Error object: ' + JSON.stringify(error)
].join(' - ');
alert(message);
}
return false;
};
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 |
---|---|---|
HTML Living Standard The definition of 'onerror' in that specification. | Living Standard |
Browser compatibility
BCD tables only load in the browser
See also
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论