Enable promise rejection event
Categories
(Core :: DOM: Core & HTML, enhancement, P2)
Tracking
()
People
(Reporter: edgar, Assigned: edgar)
References
Details
(Keywords: dev-doc-complete)
Attachments
(4 files, 3 obsolete files)
| Assignee | ||
Updated•7 years ago
|
| Assignee | ||
Comment 1•7 years ago
|
||
It will cause the result of some tests to change, given that testharness.js is meant to fail if there are unhandled rejections [1].
| Assignee | ||
Comment 2•7 years ago
|
||
Updated•7 years ago
|
Updated•6 years ago
|
| Assignee | ||
Comment 3•6 years ago
|
||
| Assignee | ||
Comment 4•6 years ago
|
||
| Assignee | ||
Comment 5•6 years ago
|
||
which causes the promise being rejected and testharness reports error given
that there are unhandled rejected promises
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 6•6 years ago
|
||
| Assignee | ||
Comment 7•6 years ago
|
||
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 9•6 years ago
|
||
Comment 10•6 years ago
|
||
| bugherder | ||
| Assignee | ||
Comment 11•6 years ago
|
||
Updated•6 years ago
|
| Assignee | ||
Comment 12•6 years ago
|
||
| Assignee | ||
Comment 13•6 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
| Assignee | ||
Comment 14•6 years ago
|
||
Comment 15•6 years ago
|
||
| Assignee | ||
Comment 16•6 years ago
|
||
Comment 17•6 years ago
|
||
| bugherder | ||
| Assignee | ||
Comment 18•6 years ago
|
||
| Assignee | ||
Comment 19•6 years ago
|
||
Comment 20•6 years ago
|
||
Comment 23•6 years ago
|
||
| bugherder | ||
Comment 25•6 years ago
|
||
pref dom.promise_rejection_events.enabled default value should be changed to true
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 26•6 years ago
|
||
Enabling on nightly only doesn't work because it will cause the test starts to fail after merged into beta or release. So we should just enable on everywhere.
Updated•6 years ago
|
| Assignee | ||
Updated•6 years ago
|
Comment 27•6 years ago
|
||
Comment 28•6 years ago
|
||
| bugherder | ||
| Assignee | ||
Updated•6 years ago
|
Comment 29•6 years ago
|
||
Since the status are different for nightly and release, what's the status for beta?
For more information, please visit auto_nag documentation.
Comment 30•6 years ago
|
||
(In reply to Release mgmt bot [:sylvestre / :calixte] from comment #29)
Since the status are different for nightly and release, what's the status for beta?
For more information, please visit auto_nag documentation.
As this is to enable a new feature on 69, I think we should move status-firefox67 and status-firefox68 to default ---.
Comment 31•6 years ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: While implementing Promises, developers need to handle rejections and catch them accordingly, but sometimes they may not. This feature is useful for debugging, for general application resiliency, and for providing fallback error handling for unexpected situations.
[Affects Firefox for Android]: yes
[Suggested wording]:
[Links (documentation, blog post, etc)]: https://developer.mozilla.org/en-US/docs/Web/API/PromiseRejectionEvent
Comment 32•6 years ago
|
||
Announced here: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/69#JavaScript
Docs were already updated per https://bugzilla.mozilla.org/show_bug.cgi?id=1362272#c17
Compat table looks up to date to me, too: https://developer.mozilla.org/en-US/docs/Web/API/PromiseRejectionEvent#Browser_compatibility
(we don't mark this as shipping Firefox Android 69 as 68 is the last Android we've shipped per https://groups.google.com/forum/#!topic/mozilla.dev.platform/k-irJtmCcqg)
Comment 33•6 years ago
|
||
I think updating MDN is sufficient here without adding this to the Fx69 relnotes. Feel free to NI me if you feel strongly otherwise.
Description
•