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.

Sign up for GitHub

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

Jump to bottom

BUG: nextTick scheduler throwing when calling setImmediate in Chrome #690

Closed
benlesh opened this issue Nov 10, 2015 · 3 comments · Fixed by #691 or #694
Closed

BUG: nextTick scheduler throwing when calling setImmediate in Chrome #690

benlesh opened this issue Nov 10, 2015 · 3 comments · Fixed by #691 or #694
Assignees
@benlesh
Labels
bug Confirmed bug

Comments

@benlesh
Copy link
Member

benlesh commented Nov 10, 2015

Looks like an oversight on my part. Here is a JSBin demoing the broken behavior.
@benlesh benlesh added the bug Confirmed bug label Nov 10, 2015
@benlesh benlesh self-assigned this Nov 10, 2015
@benlesh benlesh mentioned this issue Nov 10, 2015
Merged
@benlesh
Copy link
Member Author

benlesh commented Nov 10, 2015

It's still a problem. :\

@benlesh benlesh reopened this Nov 10, 2015
@benlesh benlesh mentioned this issue Nov 10, 2015
Merged
@kwonoj
Copy link
Member

kwonoj commented Nov 10, 2015

Is it repro on all chrome instances? I've able to repro with attached JSBin onetime, and following attempt does not shows same results.

@benlesh
Copy link
Member Author

benlesh commented Nov 10, 2015

@kwonoj I've got it fixed now. I could reproduce it in JSBin. It was a silly mistake. All better now.

@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.
Assignees

@benlesh benlesh

Labels
bug Confirmed bug
Projects
None yet
Milestone
No milestone
2 participants
@kwonoj @benlesh