Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)

To briefly summarize the WHATNOT [meeting discussion about this issue](https://github.com/whatwg/html/issues/10215#issuecomment-2025701581), we tentatively landed on:
- Moving this to stage 1  🎉 
- Not pursuing an iframe-specific solution, but handling the big known use cases in https://reparent.jarhar.com/ up-front
- Pursuing a generic DOM API that would use a new "move" DOM primitive operation
    - This API would **not** have a bag of options to specify what kind of state should be preserved, but would preserve all of "the big known things" captured in https://reparent.jarhar.com/
    - The compat risk of, in the future, adding possibly-new forms of preservable state that would begin to be preserved by the API, seems "manageable." (The risk of this is at least in part ameliorated by the fact that author JS can opt out of the preservation for any part of any moved subtree, just by removing and re-inserting nodes)

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

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