为什么 JavaScript NodeList 是不可变的？
最近我发现元素的 childNodes 属性返回 NodeList 而不是数组。现在我明白 NodeList 应该是元素的实时集合，但我不明白为什么这会阻止它使用像 indexOf 甚至 Push 这样的方法。
谁能解释一下为什么对 NodeList 唯一能做的就是索引它？
Recently I came across the fact that the childNodes property of an element returns a NodeList and not an Array. Now I understand that a NodeList is meant to be a live collection of elements, but I don't get why that precludes it having methods like indexOf, or even push.
Could anyone explain why the only thing you can do with a NodeList is index it?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
因为这就是它指定的方式。 DOM API 是与 JavaScript 分开设计的。事实上，
NodeList与 JavaScript 数组有一些共同点（长度和索引）只是......好吧，这实际上可能不是一个巧合 ，而是设计过程中投入的副产品。请记住，JavaScript 并不是唯一具有 DOM 绑定的语言。您可以使用 DOM API 轻松影响
NodeList的内容：...或者当然是您最喜欢的 JavaScript 库。
Because that's the way it's specified. The DOM API was designed separately from JavaScript. The fact that
NodeListhas some common aspects with JavaScript arrays (lengthand indexing) is just...well, it's probably not actually a coincidence, but a by-product of inputs into the design process. Remember that JavaScript is not the only language that has DOM bindings.You can readily affect the contents of a
NodeListusing the DOM API:...or of course, your favorite JavaScript library.
我的印象是，在这种情况下，您必须使用正确的 DOM 机制来更改 DOM 结构。
看看它的兼容性问题，无论如何使用 DOM 方法可能更安全：
http://reference.sitepoint.com/ javascript/NodeList
I was under the impression that this was the case so that you'd have to use the proper DOM mechanisms for altering DOM structures.
Looking at it's compatibility problems, it's probably safer to use DOM methods anyway:
http://reference.sitepoint.com/javascript/NodeList