A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://developer.mozilla.org/en-US/docs/Web/API/WorkerGlobalScope/rejectionhandled_event below:

WorkerGlobalScope: rejectionhandled event - Web APIs

WorkerGlobalScope: rejectionhandled event

Baseline Widely available

Note: This feature is only available in Web Workers.

The rejectionhandled event is sent to the script's global scope (typically WorkerGlobalScope) whenever a rejected Promise is handled late, i.e., when a handler is attached to the promise after its rejection had caused an unhandledrejection event.

This can be used in debugging and for general application resiliency, in tandem with the unhandledrejection event, which is sent when a promise is rejected but there is no handler for the rejection at the time.

Syntax

Use the event name in methods like addEventListener(), or set an event handler property.

addEventListener("rejectionhandled", (event) => { })

onrejectionhandled = (event) => { }
Event type Event properties
PromiseRejectionEvent.promise Read only

The Promise that was rejected.

PromiseRejectionEvent.reason Read only

A value or Object indicating why the promise was rejected, as passed to Promise.reject().

Example

You can use the rejectionhandled event to log promises that get rejected to the console, along with the reasons why they were rejected:

self.addEventListener("rejectionhandled", (event) => {
  console.log(`Promise rejected; reason: ${event.reason}`);
});
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.4