124066 2013-11-08 13:15:57 -0800 Uncaught exceptions raised in promise completion functions are not printed to console 2017-04-27 20:37:48 -0700 1 1 1 Unclassified WebKit Web Inspector 528+ (Nightly build) Unspecified Unspecified RESOLVED DUPLICATE 150358 https://bugs.webkit.org/show_bug.cgi?id=147502 InRadar P2 Normal --- 1 ap webkit-unassigned bfulgham graouts inspector-bugzilla-changes joepeck sam webkit-bug-importer oldest_to_newest 948810 0 216429 ap 2013-11-08 13:15:57 -0800 Created attachment 216429 test case E.g. crypto.subtle.generateKey({name: "hmac", hash: "sha-1"}, true, ["sign", "verify"]).then(function(result) { throw("See me?"); }); Marking this as blocking WebCrypto, because it's super difficult to use WebCrypto form JS when uncaught exceptions are not visible in Inspector. In fact, this is even slowing down writing tests for me, even though I'm only targeting WebKit, and know what and when raises exceptions. 955695 1 218241 ap 2013-12-02 16:57:39 -0800 Created attachment 218241 another test case A test case that doesn't use WebCrypto. What happens here is when JSPromiseWrapperCallback::callPromiseWrapperCallback() sees an exception, it immediately clears it, and invokes resolver's reject callback with the exception as argument. But when there are no reject callbacks registered, it's just dropped on the floor. Perhaps the exception shouldn't be cleared when there are no reject callbacks to handle it, and then JSGlobalObjectCallback could report it in the same way as other code that executes JS does. ScriptController::evaluateInWorld() and JSEventListener::handleEvent() seem like they could serve as models. 1026921 2 joepeck 2014-08-05 12:14:30 -0700 This sounds bad! The Web Inspector should know about all exceptions. 1026922 3 webkit-bug-importer 2014-08-05 12:14:38 -0700 <rdar://problem/17920074> 1259311 4 joepeck 2016-12-12 18:48:08 -0800 There is already some work in this area on bug 150358. With the HTML Spec's unhandledpromiserejection / rejectionhandled events. 1302465 5 joepeck 2017-04-27 20:37:48 -0700 This was addressed by: bug 150358 • The first test case is outdated (there is no Promise.fulfill anymore) • The second test case produces: [Error] Unhandled Promise Rejection: See me? *** This bug has been marked as a duplicate of bug 150358 *** 216429 2013-11-08 13:15:57 -0800 2013-11-08 13:15:57 -0800 test case exception.html text/html 358 ap PCFET0NUWVBFIGh0bWw+CjxodG1sPgo8Ym9keT4KPHA+VGhlcmUgaXMgYW4gdW5jYXVnaHQgZXhj ZXB0aW9uIHJhaXNlZCBoZXJlLCBpdCBzaG91bGQgYmUgcHJpbnRlZCB0byBjb25zb2xlLjwvcD4K PHNjcmlwdD4KaWYgKCF3aW5kb3cuc3VidGxlKQogICAgd2luZG93LmNyeXB0by5zdWJ0bGUgPSB3 aW5kb3cuY3J5cHRvLndlYmtpdFN1YnRsZTsKCmNyeXB0by5zdWJ0bGUuZ2VuZXJhdGVLZXkoe25h bWU6ICJobWFjIiwgaGFzaDogInNoYS0xIn0sIHRydWUsIFsic2lnbiIsICJ2ZXJpZnkiXSkudGhl bihmdW5jdGlvbihyZXN1bHQpIHsKICAgIHRocm93KCJTZWUgbWU/Iik7Cn0pOwo8L3NjcmlwdD4K PC9ib2R5Pgo8L2h0bWw+Cg== 218241 2013-12-02 16:57:39 -0800 2013-12-02 16:57:39 -0800 another test case exception.html text/html 314 ap PCFET0NUWVBFIGh0bWw+CjxodG1sPgo8Ym9keT4KPHNjcmlwdD4KCndpbmRvdy5vbmVycm9yID0g ZnVuY3Rpb24oZXJyb3IpIHsgYWxlcnQoIm9uZXJyb3I6ICIgKyBlcnJvcikgfTsKClByb21pc2Uu ZnVsZmlsbChudWxsKS50aGVuKGZ1bmN0aW9uKCkgewogICAgdGhyb3cgImFhIjsKfSwgZnVuY3Rp b24oKSB7CiAgICBhbGVydCgiSW4gcmVqZWN0IGZ1bmN0aW9uIDEiKQp9KS8qLnRoZW4odW5kZWZp bmVkLCBmdW5jdGlvbigpIHsKICAgIGFsZXJ0KCJJbiByZWplY3QgZnVuY3Rpb24gMiIpCn0pOyov Cgo8L3NjcmlwdD4KCjwvYm9keT4KPC9odG1sPgo=