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

> those property bags have a GC impact so they can be more expensive than try/catch blocks

those can all be an always same object to pass around though, mine was an inline example, I would write once that object and pass it every single time, no much GC pressure / impact?

>  having a moveOrInsertBefore variant (early or soon after) would also work

my thinking is that having `moveBefore` symmetric with `insertBefore` is the most desired feature so that it's current behavior that will backfire ... but about your use case, what does the developer do once that error occurs? What are the next steps when such move can't be performed? Silently fail on user surfing side or ... what else?

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

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