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

NodeList #34

Open
mindplay-dk opened this issue Apr 11, 2021 · 0 comments
Open

NodeList #34

mindplay-dk opened this issue Apr 11, 2021 · 0 comments

Comments

@mindplay-dk
Copy link

I tried using this for a unit-test, and ran into some issues with e.g. childNodes, which in regular DOM is a 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?

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

1 participant