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

The more I think about that, the more that I realize how fragile it would be wrt manipulation order. It's easy to first replace some nodes that you would later move somewhere else. A properly atomic move api absolutely needs to have transactions to avoid this. The easiest solution is to just make transactions commit in the next microtask. I'm pretty sure this is the same behavior that the current manipulation apis have, but I just want to confirm that this is how `moveBefore()` _&c._ will behave.

I think it's worth it to talk about this sooner rather than later, but I'm pretty sure that this should be in a separate issue.

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

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