-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled rejection tracking and native promises #140
Labels
Comments
Now that they're in the spec, +1 for replacing a native |
Added to feature detection in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Most V8
Promise
bugs (like 1 or 2) will be fixed in V8 ~ Chrome 49. Still not fixed V8 bugs are fixed incore-js
by patching methods. It means custom unhandled rejection handlers will not work in Chrome 49 withcore-js
. The same situation with FF46. Some days ago promise rejection events was added to ECMAScript and HTML drafts.So the question for the community: replace native
Promise
without support promise rejection events (in this case, in addition to global handlers, add generation custom events in browsers) or not?Upd.: Ok. Chrome 49 supports unhandled rejection events.
Upd.: Because some other bugs, native
Promise
should be available only in V8 ~ Chrome 51.The text was updated successfully, but these errors were encountered: