You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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 anArray
, which is missing, for example, thekeys()
,values()
andentries()
iterator methods.I can foresee issues as well with e.g.
children
being a plainArray
created by filteringchildNodes
- whereas, in regular DOM, mutating thechildNodes
of the parent that generated thechildren
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?
The text was updated successfully, but these errors were encountered: