<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Support for promise rejection events"
href="https://bugs.webkit.org/show_bug.cgi?id=150358#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Support for promise rejection events"
href="https://bugs.webkit.org/show_bug.cgi?id=150358">bug 150358</a>
from <span class="vcard"><a class="email" href="mailto:richardconnamacher@gmail.com" title="Richard Connamacher <richardconnamacher@gmail.com>"> <span class="fn">Richard Connamacher</span></a>
</span></b>
<pre>This feature is now in the ECMAScript and HTML standards.
ECMAScript 2016 defines when the host's unhandled promise rejection events should fire:
<a href="http://www.ecma-international.org/ecma-262/7.0/#sec-host-promise-rejection-tracker">http://www.ecma-international.org/ecma-262/7.0/#sec-host-promise-rejection-tracker</a>
HTML Living Standard defines the window unhandledrejection and rejectionhandled events:
<a href="https://html.spec.whatwg.org/multipage/webappapis.html#unhandled-promise-rejections">https://html.spec.whatwg.org/multipage/webappapis.html#unhandled-promise-rejections</a>
These events have thus far been implemented in Chrome and Node.
This is very useful, since uncaught (and unhandled) errors thrown inside promises are not seen by the window.onerror event, and in Safari do not even cause a message to be printed to the console. They just disappear silently into the ether. The unhandledrejection event fixes that, like window.onerror for promises.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>