Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)

> IMHO _re-ordering_ is the most needed feature in the majority of frameworks/libraries, less _re-parenting_, so why not start with a simpler method to cover this specific use case, such as `targetNode.move(beforeNode)`, until the `moveBeforeOrInsert` mammoth is eventually conceived?

@syduki As long as it remains in the same document, there really isn't much difference between moving within the same parent and giving it a new parent.

Plus, existing DOM APIs have the same state and animation resetting behavior regardless of whether it's in the same parent or moved to another parent. So doing it this way is more consistent with the current state of things than what you're proposing.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/1255#issuecomment-2596701848
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/issues/1255/2596701848@github.com>