Bug 281223
| Summary: | [DOM] Element.moveBefore() API | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Dominic Farolino <domfarolino> |
| Component: | DOM | Assignee: | Luke Warlow <lwarlow> |
| Status: | ASSIGNED | ||
| Severity: | Normal | CC: | 709922234, agafvv, andseier, annevk, apolostudioapps, cdumez, karlcow, lwarlow, mattwalker340, messes.tombs.3x, ntim, pinkhominid, unilynx, webkit-bug-importer, woodlxf00 |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 314066, 317287, 321178, 312161, 312384, 312983, 313148, 313719, 314067, 315096, 315754, 316098, 323107, 326182 | ||
| Bug Blocks: | |||
Dominic Farolino
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
<rdar://problem/138111357>
Karl Dubost
The standard position is marked as support: positive.
https://github.com/WebKit/standards-positions/issues/375
andseier
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
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
Apolo
Yep, looking forward to this.