Add 'next sibling' source relevant mutation test#51381
Merged
Merged
Conversation
6 tasks
See whatwg/html#11113. Since the test added here passes in all browsers, we can remove the spec text indicating that the source element's removing and moving steps somehow keep track of the previous position's "next sibling" pointer. See also whatwg/html#11137. R=domenic Bug: N/A Change-Id: I572939ee5f7acb0c8980707a46aa581c449eb96d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6357453 Reviewed-by: Domenic Denicola <domenic@chromium.org> Commit-Queue: Dominic Farolino <dom@chromium.org> Cr-Commit-Position: refs/heads/main@{#1433512}
ee8db68 to
d66443f
Compare
wpt-pr-bot
approved these changes
Mar 17, 2025
wpt-pr-bot
left a comment
Collaborator
There was a problem hiding this comment.
The review process for this patch is being conducted in the Chromium project.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See whatwg/html#11113. Since the test added
here passes in all browsers, we can remove the spec text indicating
that the source element's removing and moving steps somehow keep track
of the previous position's "next sibling" pointer.
See also whatwg/html#11137.
R=domenic
Bug: N/A
Change-Id: I572939ee5f7acb0c8980707a46aa581c449eb96d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6357453
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Commit-Queue: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1433512}