281223 2024-10-10 07:23:44 -0700 [meta] Implement atomic moveBefore() API 2026-05-10 13:04:03 -0700 1 1 1 Unclassified WebKit DOM WebKit Nightly Build Unspecified Unspecified ASSIGNED InRadar P2 Normal --- 313148 314066 314067 312161 312384 312983 313719 1 domfarolino lwarlow 709922234 agafvv andseier annevk cdumez karlcow lwarlow mattwalker340 pinkhominid unilynx webkit-bug-importer woodlxf00 oldest_to_newest 2066893 0 domfarolino 2024-10-10 07:23:44 -0700 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 2068763 1 webkit-bug-importer 2024-10-17 07:24:14 -0700 <rdar://problem/138111357> 2145450 2 karlcow 2025-09-23 21:31:35 -0700 The standard position is marked as support: positive. https://github.com/WebKit/standards-positions/issues/375 2163902 3 andseier 2025-12-06 12:40:49 -0800 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 2170192 4 mattwalker340 2026-01-08 01:14:59 -0800 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