We consider it a mistake in the platform that element movement is handled by removing and then re-inserting nodes. We would prefer if this effort fixed the existing methods rather than adding new methods. Could the designers invest in some more thorough testing to see if this breaks a significant number of pages, rather than just [assuming](https://github.com/noamr/dom/blob/spm-explainer/moveBefore-explainer.md#changing-the-default-behavior) that it will? If changing all of the element-movement methods does break things, perhaps it would be compatible to change only the newer ones that are methods on `ParentNode` and `ChildNode`. In that case, we think the slight inconsistency between, e.g., `append()` and `appendChild()` is worth the more intuitive behavior on the newer method. Thank you for bringing this to us. The WHATWG discussion seems like the right place to dig into the compatibility question, so we're happy to let them take it from here. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/976#issuecomment-2359457221 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/976/2359457221@github.com>
Received on Wednesday, 18 September 2024 21:43:48 UTC