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

@noamr I guess my point is that if there are no concrete performance benefits because both user-land code and native code needs to perform *twice* the same checks to be sure it's not going to throw, this APIs won't really benefit much anyone, except for those cases where the state is preserved which is surely desired, but usually that's not the main use case for move nodes operations ... you can see lit having that just on rows reording or containers reordering, it's not that Web developers should move inputs around while you're typing, if you understand what I am talking about ... I hope try/catch won't degrade too much perfs though, but I'd be reluctant to do on my side what inevitably happens also behind the scene after I've done all those user-land checks before calling `moveBefore` ... I see duplication and CPU wasted all over, imho ... but maybe benchmarks will show otherwise.

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

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