Closed
Bug 1253371
Opened 8 years ago
Closed 8 years ago
Figure out what to do with Promises and uncatchable exceptions
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
People
(Reporter: khuey, Assigned: khuey)
Details
(Whiteboard: [Comment 4 is about bug 1253370] btpp-fixlater)
Consider var p = new Promise(function(resolve, reject) { while (1); }); When the user aborts the iloop via the slow script dialog, we throw an uncatchable exception. For any other exception we would reject the promise with that exception, but rejecting a Promise with an uncatchable exception is more than a little bit nonsense.
Comment 1•8 years ago
|
||
My gut feeling is we should rethrow the uncatchable exception out of the Promise ctor in this situation, fwiw.
Comment 2•8 years ago
|
||
And for then callbacks probably just neither resolve nor reject the next promise.
Updated•8 years ago
|
Whiteboard: btpp-fixlater
Assignee | ||
Comment 3•8 years ago
|
||
Implemented in bug 1252268.
Assignee: nobody → khuey
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Comment 4•8 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/71eb251a0f29de94082623b91326e2449a3aa81e Bug 1253371 - make atomics range checking conformant. r=jolesen
Comment 5•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/71eb251a0f29
Comment 6•8 years ago
|
||
Lars, I assume you mistyped the bug# in your commit? Mind putting the right bug# in the whiteboard here?
Flags: needinfo?(lhansen)
Updated•8 years ago
|
Whiteboard: btpp-fixlater → [Comment 4 is about bug 1253370] btpp-fixlater
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•