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

fix(Immediate): set immediate should no longer throw in Chrome #694

Merged
merged 1 commit into from
Nov 10, 2015
Merged

fix(Immediate): set immediate should no longer throw in Chrome #694

merged 1 commit into from
Nov 10, 2015

Conversation

benlesh
Copy link
Member

@benlesh benlesh commented Nov 10, 2015

closes #690

@benlesh benlesh merged commit a3de7d9 into ReactiveX:master Nov 10, 2015
@benlesh benlesh deleted the omg-fix-again branch April 27, 2016 17:20
@lock
Copy link

lock bot commented Jun 7, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG: nextTick scheduler throwing when calling setImmediate in Chrome
1 participant