- From: Dominic Farolino <notifications@github.com>
- Date: Tue, 26 Mar 2024 20:49:12 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 27 March 2024 03:49:15 UTC
> I don't think we can make this happen automatically based on a content attribute on an iframe. It most certainly needs to be a completely new DOM API. I am very much open to that, I'm just trying to consider what subtree side-effects are acceptable. That is, if `parent.appendAtomic(connectedDivWithChildIframe)` should preserve the "child iframe" state or not? I think it has to, for the API to be useful at all. But I'm also sympathetic to compat concerns that it might cause a preserving-move to happen on deeply-nested iframes in a subtree built by another application/framework than the one _performing_ the move in the first place. (And maybe that could break things if parts of the app relies on preserving moves _not_ happening on nodes in the subtree). -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/1255#issuecomment-2021871748 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/1255/2021871748@github.com>
Received on Wednesday, 27 March 2024 03:49:15 UTC