-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Implement NodeList.prototype.forEach()
#329
Comments
I'd volunteer for the implementation of this polyfill :) |
@christiansany DO IT! |
Added to v3 branch. |
Hey whats the current status of this? Do you need any help? |
It's checked in v3 PR. |
Hello, It doesn't work. I use Webpack. entry: {
app: ['@babel/polyfill', './src/css/style.scss', './src/js/app.js'],
}, input : document.querySelectorAll('.test').forEach(el => {
console.log(el)
}) output : document.querySelectorAll('.test').forEach(function (el) {
console.log(el);
}); So I have this expected error on IE11 : I expected something like that : [].call.forEach(document.querySelectorAll('.test'), function (el) {
console.log(el);
}); Did I miss something ? |
So… @zloirock, what about v3 release? PR was merged, three betas were released, and no new beta since early June. |
Oh yes.. I didn't notice that. Thanks for the answer. |
no new releases since june? |
Running into this same issue and would love to see a forEach polyfill get merged in 👍 |
…ction prototypes These appear to be added to address zloirock#329. However, only NodeList and DOMTokenList are documented and tested to have these functions on their prototypes.
…ction prototypes These appear to be added to address zloirock#329. However, only NodeList and DOMTokenList are documented and tested to have these functions on their prototypes.
These appear to be added to address zloirock#329. However, only NodeList and DOMTokenList are documented and tested to have forEach on their prototypes.
should you implement this?
https://developer.mozilla.org/en-US/docs/Web/API/NodeList/forEach
The text was updated successfully, but these errors were encountered: