NEW281223
Implement atomic moveBefore() API 
https://bugs.webkit.org/show_bug.cgi?id=281223
Summary Implement atomic moveBefore() API
Dominic Farolino
Reported 2024-10-10 07:23:44 PDT
This is a tracking bug for the WebKit implementation of the moveBefore() API: See: - https://github.com/whatwg/dom/issues/1255 - https://github.com/whatwg/dom/pull/1307 - https://github.com/whatwg/html/pull/10657 - https://github.com/WebKit/standards-positions/issues/375
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2024-10-17 07:24:14 PDT
<rdar://problem/138111357>
Karl Dubost
Comment 2 2025-09-23 21:31:35 PDT
The standard position is marked as support: positive. https://github.com/WebKit/standards-positions/issues/375
andseier
Comment 3 2025-12-06 12:40:49 PST
Any updates here? It appears to be formally in the specification and has been supported by Chrome and Firefox. For context, the `moveBefore` API helps me avoid unnecessary work in the `connectedCallback` / `disconnectedCallback` (which is currently unavoidable without using `moveBefore`). Thanks for reading <3
mattwalker340
Comment 4 2026-01-08 01:14:59 PST
It seems that all of the linked issues have been closed - what are we waiting on before this will be integrated into Safari? As andseier says I am waiting for much better lifecycle usage in web components, and we can't integrate improvements into our platform until this is supported in Safari
Note You need to log in before you can comment on or make changes to this bug.