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

Fixes #188: setImmediate fallbacks when unavailable. #190

Merged
merged 1 commit into from
May 10, 2016

Conversation

n1k0
Copy link
Collaborator

@n1k0 n1k0 commented May 5, 2016

Refs #188, cc @rossnanop

@n1k0
Copy link
Collaborator Author

n1k0 commented May 8, 2016

Note that this would introduce the bug reported in #194. requestAnimationFrame doesn't seem to be a viable drop-in fallback to setImmediate.

We need a decent universal polyfill here, and setimmediate looks to be the natural candidate.

@n1k0 n1k0 force-pushed the 188-setimmediate-fallbacks branch 3 times, most recently from af224d1 to 9140cd3 Compare May 10, 2016 08:58
@n1k0 n1k0 force-pushed the 188-setimmediate-fallbacks branch from 9140cd3 to 1cb0d16 Compare May 10, 2016 09:01
@n1k0 n1k0 merged commit a2803fa into master May 10, 2016
@n1k0 n1k0 deleted the 188-setimmediate-fallbacks branch May 10, 2016 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant