The reportError()
method of the Window
interface may be used to report errors to the console or event handlers of global scopes, emulating an uncaught JavaScript exception.
This feature is primarily intended for custom event-dispatching or callback-manipulating libraries. Libraries can use this feature to catch errors in callback code and re-throw them to the top level handler. This ensures that an exception in one callback will not prevent others from being handled, while at the same time ensuring that stack trace information is still readily available for debugging at the top level.
Syntax Parametersthrowable
An error object such as a TypeError
.
None (undefined
).
TypeError
The method is called without an error argument.
Feature test for the method using:
if (typeof window.reportError === "function") {
// function is defined
}
The following code shows how you might create and report an error, and how it may be caught using either the onerror
event handler property or by adding a listener for the error
event. Note that the handler assigned to onerror
must return true
to stop the event propagating further.
const newError = new Error("Some error message", "someFile.js", 11);
window.reportError(newError);
window.onerror = (message, source, lineno, colno, error) => {
console.error(`message: ${error.message}, lineno: ${lineno}`);
return true;
};
window.addEventListener("error", (error) => {
console.error(error.filename);
});
// Output
// > "message:Some error message, lineno: 11"
// > "someFile.js"
Specifications Browser compatibility See also
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3