Repository navigation
DOM State-Preserving Move: moveBefore() #1034
Description
Description
The new moveBefore() function offers developers a way to move elements within the DOM without losing various states.
https://developer.mozilla.org/en-US/docs/Web/API/Element/moveBefore
https://developer.mozilla.org/en-US/docs/Web/API/Document/moveBefore
https://developer.mozilla.org/en-US/docs/Web/API/DocumentFragment/moveBefore
Specification
https://dom.spec.whatwg.org/#dom-parentnode-movebefore
web-feature
move-before
Test Links
https://wpt.fyi/results/dom/nodes/moveBefore
Additional Signals
Reacted by Gustav Hansen, Oliver Williams, Ana Tudor, Christopher Kirk-Nielsen, Andrew Bone, Johan Lindkvist, Noam Rosenthal, G. Luke Mendelman-Haenn, Luke Warlow, Owen Buckley and 32 more
Reacted by Jayden Pearse
Activity
github-actions commentedon Sep 5, 2025
This comment was automatically generated based on the information you provided. Please don't edit it.
Below is additional information about the web feature (from the web-features project) which is referenced in your proposal.
If this doesn't accurately correspond to your proposal, please update your initial comment to include
web-features: <feature-id>.To find feature IDs, use the web-features explorer.
Feature moveBefore()
moveBefore()DOM method relocates a node while preserving its state. For example, you can move the active element without losing focus, move an animated element without resetting the animation, or move an iframe without reloading its content.o-t-w commentedon Sep 14, 2025
moveBeforeis available in Firefox Beta and should land in Firefox stable 144.smaug---- commentedon Sep 16, 2025
FWIW, some of the selection tests rely heavily on Chromium internal behavior and shouldn't be part of the interop, or should be rewritten to follow the specs.
jspurlin commentedon Sep 29, 2025
Office Online (Excel, OneNote, PowerPoint, Visio, and Word) is super excited about this functionality, will be utilizing it, and can't wait for broader browser support!!!
gsnedders commentedon Sep 30, 2025
Presumably some of the https://wpt.fyi/results/dom/nodes/moveBefore/selection-preserve.html?label=master&label=experimental&aligned subtests?
smaug---- commentedon Sep 30, 2025
Yes, https://searchfox.org/firefox-main/rev/9140dac1eab834541a75792a78a5ed2fbee39142/testing/web-platform/tests/dom/nodes/moveBefore/selection-preserve.html#37-55
And also tests for render-blocking
https://searchfox.org/firefox-main/source/testing/web-platform/tests/dom/nodes/moveBefore/preserve-render-blocking-script.html
https://searchfox.org/firefox-main/source/testing/web-platform/tests/dom/nodes/moveBefore/preserve-render-blocking-style.html
shouldn't be part of interop, unless render-blocking itself is.
zcorpan commentedon Nov 19, 2025
Should
connectedMoveCallback()be in scope?smaug---- commentedon Nov 20, 2025
yes, that is pretty core part of the API, when it comes to integration with Custom Elements.
wpt-interop commentedon Feb 12, 2026
Thank you for proposing DOM State-Preserving Move:
moveBefore()for Interop 2026.We want to let you know it was not selected to be part of Interop this year.
On behalf of the entire Interop team, thank you for submitting it for consideration. We got many more proposals than we could include in this year's project, necessitating some difficult choices. Please note this should not be taken as a comment on the technology as a whole, or our willingness to consider it for Interop in the future. We appreciate the work you put into your proposal, and would welcome your participation in future rounds of Interop.
Posted on behalf of the Interop team.