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

> This makes me sad because there was no real conversation around users' presented use cases and the solution is that "_we_" are landing a new API that requires mandatory `try/catch` around its execution, which is the opposite direction other more recent APIs took, such as `node.remove()`, which works even if the node is not even live.

I think this the core point here - the newer APIs went into a "higher level" ergonomic direction, which is great. But `moveBefore` is the first API that exposes the "moving" concept. So there is value in keeping it as low level as possible, and deferring the ergonomic magic to future APIs, which can emerge from userland JS at first.


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

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