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

Anything using `moveBefore` will fallback to `insertBefore` no matter what. There's literally 0 use-cases for throwing. 

@dead-claudia comment from here https://github.com/whatwg/dom/pull/1307#issuecomment-2492406859
An acceptable compromise would be adding a flag to make it throw
- `parent.moveBefore(child, refNode)` fallback to `insertBefore` if needed
- `parent.moveBefore(child, refNode, true)` throws if needed

That, or every framework will have to ship the same 5 lines of code (if that doesn't make this ridiculous slow, on which case they will restore focus/selection in other ways and skip using this api)

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

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