NodeList

I tried using this for a unit-test, and ran into some issues with e.g. `childNodes`, which in regular DOM is a [NodeList](https://developer.mozilla.org/en-US/docs/Web/API/NodeList) and not just an `Array`, which is missing, for example, the `keys()`, `values()` and `entries()` iterator methods.

I can foresee issues as well with e.g. `children` being a plain `Array` created by filtering `childNodes` - whereas, in regular DOM, mutating the `childNodes` of the parent that generated the `children` collection, would cause the iterator to reflect those changes.

Maybe this is "by design", favoring simplicity over correctness?

If so, that isn't clear from the "Project Goals" stated in the README right now - it doesn't seem to imply that this deviates from DOM in terms of more than features.

Lacking features is a matter of scope - but incompatibilities probably ought to be designated in the documentation?

Comienza con los Project Goals del README e inspecciona cómo se producen actualmente childNodes y children. Compara el comportamiento con los métodos keys(), values() y entries() de NodeList y con las expectativas de mutación/liveness indicadas. Para darlo por terminado, se requiere una decisión clara sobre el alcance de compatibilidad, ya sea con desviaciones documentadas o con un cambio de implementación acotado y pruebas.

Escrito por el modelo de indexación a partir del texto del issue.