WebContentsDidFailLoadEvent
WebContentsDidFailLoadEvent represents a web page that failed to load.
The did-fail-load event of WebContents is this class. It carries the system error code, its description, and the URL that failed. A 404 or 500 from the server doesn't count as a failure.
Inheritance: Event → WebContentsDidFailLoadEvent
Constructor
Creates a WebContentsDidFailLoadEvent. The runtime creates one itself when it fires the events below; app code can use it to build an event object and fire it with dispatchEvent() to try out a listener.
Instance properties
Also inherits the properties of Event; the most commonly used are type and target. The properties below are read-only; assigning to them throws TypeError.
| Property | Description |
|---|---|
errorCode read-only | The system error code |
errorDescription read-only | A text description of the error |
validatedURL read-only | The URL that failed to load |
isMainFrame read-only | Always true |
These properties live on the prototype, not on the event object itself: Object.keys(event) and { ...event } don't include them, so read them one by one. See Events with fields.
Events that use this class
| Object | Events |
|---|---|
WebContents | did-fail-load |
It can't be canceled: cancelable is false, and preventDefault() has no effect.
Examples
const contents = new WebView().webContents;
contents.addEventListener('did-fail-load', (e) => {
console.log(e instanceof WebContentsDidFailLoadEvent, e.errorCode, e.validatedURL);
});
contents.loadURL('https://no-such-host.invalid').catch(() => {});Effect: the load fails and prints true, the error code (such as -1003), and the URL that failed.
Corresponding iOS API
There is no corresponding system API. The event name and field names follow the event of the same name on Electron's webContents. The error codes are the system's, not Chromium's. The native equivalents are webView:didFailNavigation:withError: and webView:didFailProvisionalNavigation:withError:.
See also
did-fail-load: when it is firedWebContents