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

Follow-up to the discussion [here](https://github.com/whatwg/dom/pull/1307#issuecomment-2491906616):

To be blunt, with this API as-is I think it's likely the following will happen:
1. many web frameworks will welcome this API and attempt to leverage it to fix bugs and remove workaround code
2. framework code will need to fallback to insertBefore using try/catch or other checks
3. these checks will be needed in hot paths potentially affecting performance tests on which frameworks compete
4. if there is measurable performance degradation, frameworks will not use this API

Assuming (4) occurs, which I think is probably likely, If these checks can be done faster in platform code, they should be done there.

Perhaps the behavior here can be revisited based on developer feedback from testing of initial implementations.

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

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