Fix: If Node moved to another parent then no any action to delete is …

[anthony-redFox]

…need.

[WebReflection]

If Node moved to another parent then no any action to delete is needed

nodes don't move by themselves around, obtrusive libraries might move nodes around though but that violates the purpose of the differ which owns the elements.

this change breaks every library based on domdiff so I am afraid this won't happen.

what you maybe want is to use .remove() instead of parentNode.removeChild() but diffing across two elements makes no sense, also because you can just move all elements at once via fragment.append(...latestNodesInBody).

[anthony-redFox]

@WebReflection this is fix for use case - https://codepen.io/anthony-redfox-the-lessful/pen/BaVqLzq?editors=0010
when node was re used in another place. I expected that will be render all nodes (with fix it is works)
foo
bar
baz

The same example with Uhtml - https://codepen.io/anthony-redfox-the-lessful/pen/ExRGVoG?editors=0010
The example execute with script Error!

Can you say what I doing wrong with hyperHtml or Uhtml

[WebReflection]

The same example with Uhtml

drop the .for(...) and no error happens

Can you say what I doing wrong with hyperHtml or Uhtml

you want a single node to be simultaneously part of two different parts of the tree ... that can't happen with the DOM, so your option is to not wire the node and just use html tag as is (in uhtml).

Alternatively you can fork this project which is basically dead and use node.remove() instead of parentNode.removeChild(node) within the drop function but you have a fundamental issue with your logic, imho, and that's not worth fixing to me.