Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307)

> however it's debatable whether it's the platform's job to hide this difference for the sake of ergonomics in a somewhat low-level API like DOM.

@noamr There *is* some precedent for light ergonomics in the DOM already: `child.before`, `child.after`, `parent.append`, and `parent.replaceChildren` all four accepting strings and auto-converting them into text nodes. I feel this could qualify as such "light ergonomics".

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

Message ID: <whatwg/dom/pull/1307/c2492415097@github.com>