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

IE10/IE11 setImmediate bug #35

Open
dantman opened this issue Jul 6, 2014 · 8 comments
Open

IE10/IE11 setImmediate bug #35

dantman opened this issue Jul 6, 2014 · 8 comments

Comments

@dantman
Copy link

dantman commented Jul 6, 2014

It looks like there is a bug inside IE10+'s implementation of setImmedate:
http://codeforhire.com/2013/09/21/setimmediate-and-messagechannel-broken-on-internet-explorer-10/

It might be desirable to ignore IE's setImmedate implementation and use the onreadystatechange trick for it.

@wswoodruff
Copy link

wswoodruff commented May 9, 2017

Ha! Found this in a random Google search (Googled setimmediate ie10). Whaddup @dantman!

@ronkorving
Copy link

Any updates on this?

@domenic
Copy link
Collaborator

domenic commented Nov 10, 2017

@ronkorving
Copy link

@dantman Were you planning on making a PR for this?

@dantman
Copy link
Author

dantman commented Nov 13, 2017

@ronkorving No, I don't believe I'm even using this specific polyfill implementation anymore.

@ronkorving
Copy link

@dantman Did you find a better alternative?

@dantman
Copy link
Author

dantman commented Nov 13, 2017

@ronkorving Lately I just use whole package polyfills like core-js. Though I haven't dug into their actual implementations or determined if they have this same issue.

@ronkorving
Copy link

@dantman Understood. Thanks 👍

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

No branches or pull requests

4 participants