Add Safari bug for DOM moveBefore API#28368
Merged
Conversation
github-actions
Bot
added
data:api
Contributor
|
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
caugner
approved these changes
Nov 4, 2025
Contributor
|
Thank you! |
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
2 participants
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.
Summary
Add WebKit implementation ticket link for
Document.moveBefore,DocumentFragment.moveBefore, andElement.moveBefore.Test results and supporting details
It looks to me there is a single WebKit bug to track implementation of
moveBeforeacrossDocument,DocumentFragment, andElement: https://webkit.org/b/281223This is my first time contributing to this repo, so please let me know if there are any issues with the PR format, content, etc. I tried to format this change to be similar to #28056. Thanks!
Related issues
n/a