- From: Josh Story <notifications@github.com>
- Date: Wed, 27 Mar 2024 11:32:10 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 27 March 2024 18:32:14 UTC
@domfarolino >I guess I had in mind that the imperative API would force-SPAM-move the "state-preservable" elements in the subtree that's moving I think what Seb is saying is that React can decide if a move should be state preserving but if React added a "preserve-state" attribute to `<html />` and then some embedded application deep in the DOM does an append expecting the append to be non-state-preserving we've just altered the moves that the other application owns. Our perspective is that the mover decides the move semantics rather than the tree. So any moves done by this embedded application won't preserve state b/c that is what the application was expecting and any moves done by React would preserve state becuase React was updated to signal this intent by using a novel API -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/1255#issuecomment-2023606473 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/1255/2023606473@github.com>
Received on Wednesday, 27 March 2024 18:32:14 UTC