Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255) from Ryosuke Niwa on 2025-04-23 (public-webapps-github@w3.org from April 2025)

From: Ryosuke Niwa <notifications@github.com>
Date: Tue, 22 Apr 2025 20:36:15 -0700
To: whatwg/dom <dom@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/dom/issues/1255/2822972643@github.com>

rniwa left a comment (whatwg/dom#1255)

> However there's this limitation where I can only "move" with moveBefore to an already connected DOM. Why? Why does that limitation exist?
> 
> I mean, I can always have a "hidden bank DOM" for this, but it's kind of ugly.
> 
> So, I have this use case. Basically I'd like to be able to "temporarily detach" DOM - preserving everything about it (that is possible) - then possibly attaching it back (and if not, I could call some "release" function that will actually permanently detach it, then it can call disconnectedCallback.

"temporarily detecting a DOM node" is not something we can easily support in browser engines.


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

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

Received on Wednesday, 23 April 2025 03:36:19 UTC