Re: [whatwg/dom] Introduce `moveBefore()` state-preserving atomic move API (PR #1307) from Adam Klein on 2024-09-04 (public-webapps-github@w3.org from September 2024)

From: Adam Klein <notifications@github.com>
Date: Wed, 04 Sep 2024 11:05:50 -0700
To: whatwg/dom <dom@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/dom/pull/1307/c2329680403@github.com>

It's been a long time since I've thought about this stuff, but I'm inclined to agree with @smaug---- that creating a new type of `MutationRecord` feels unnecessary. Users of `MutationObserver` already have to do coalescing if they want to make sense of the stream of changes they observe. There are already other move-like operations, such as appending a child that's already somewhere else in the tree, which today generates two records.

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

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

Received on Wednesday, 4 September 2024 18:05:54 UTC