-
Notifications
You must be signed in to change notification settings - Fork 107
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
Comments
Ha! Found this in a random Google search |
Any updates on this? |
@dantman Were you planning on making a PR for this? |
@ronkorving No, I don't believe I'm even using this specific polyfill implementation anymore. |
@dantman Did you find a better alternative? |
@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. |
@dantman Understood. Thanks 👍 |
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.
The text was updated successfully, but these errors were encountered: