Skip to content
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

Closed
zloirock opened this issue Dec 3, 2015 · 2 comments
Closed

Unhandled rejection tracking and native promises #140

zloirock opened this issue Dec 3, 2015 · 2 comments

Comments

@zloirock
Copy link
Owner

zloirock commented Dec 3, 2015

Most V8 Promise bugs (like 1 or 2) will be fixed in V8 ~ Chrome 49. Still not fixed V8 bugs are fixed in core-js by patching methods. It means custom unhandled rejection handlers will not work in Chrome 49 with core-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.

@danharper
Copy link

Now that they're in the spec, +1 for replacing a native Promise which doesn't support the rejection events.

@zloirock
Copy link
Owner Author

Added to feature detection in 2.1.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants