commit d4c2e78045dacd7464717255bf05c730dfb6aa54
author Noam Rosenthal <nrosenthal@chromium.org> Wed Oct 09 12:59:07 2024
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Wed Oct 09 12:59:07 2024
tree c58545f6bdb4253cbc5e5652562a49e6c77f636a
parent 856366e6861f04f1d22b8b1d4e907ec585b99368

Revert "Automatically preserve state when using ParentNode/ChildNode functions"

This reverts commit 083da4ae5bcf3abce3810ae148060663d2ffbecd.

Reason for revert: decided not to pursue this following TPAC spec discussion.

Original change's description:
> Automatically preserve state when using ParentNode/ChildNode functions
>
> With this flag (AtomicMoveAuto) on, the following Node methods behave
> like moveBefore in terms of preserving state:
>
> Node.before
> Node.after
> Node.prepend
> Node.append
>
> Based on this comment from TAG review: https://github.com/w3ctag/design-reviews/issues/976#issuecomment-2359457221
>
> This allows us to test if changing the behavior of these functions
> breaks something for existing sites.
>
> Copied the existing WPTs for moveBefore, and refurbished them to use
> the existing APIs using variants.
>
>
> Bug: 367985626
> Change-Id: I1fe5ff063bc11a7d91622ad76ff19db4d6f7ae0b
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5873233
> Reviewed-by: Dominic Farolino <dom@chromium.org>
> Commit-Queue: Noam Rosenthal <nrosenthal@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1357837}

Bug: 367985626
Change-Id: I22cd265f156c36da1b63c8ec4bcf29a45a4ce235
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5920194
Commit-Queue: Noam Rosenthal <nrosenthal@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1366105}