script: Fix panic when deleting after range.deleteContents#44748
Merged
Conversation
The state of the document after `range.deleteContents` leads to the delete command to traverse to the root element and then crash. Instead, we should simply stop the loop and continue the algorithm and delete backwards. Fixes servo#44742 Signed-off-by: Tim van der Lippe <[email protected]>
|
🔨 Triggering try run (#25392739094) for Linux (WPT) |
Collaborator
|
🤖 Opened new upstream WPT pull request (web-platform-tests/wpt#59670) with upstreamable changes. |
|
Test results for linux-wpt from try job (#25392739094): Flaky unexpected result (28)
Stable unexpected results that are known to be intermittent (16)
|
|
✨ Try run (#25392739094) succeeded. |
Taym95
approved these changes
May 5, 2026
Taym95
left a comment
Member
There was a problem hiding this comment.
Nice spec alignment, deleteContents() ordering matches the spec!
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.
The state of the document after
range.deleteContentsleads to the delete command to traverse to the root element and then crash. Instead, we should simply stop the loop and continue the algorithm and delete backwards.Also added an additional test I created when trying to figure out what other browsers are doing
and added spec comments to
deleteContents. Lastly, also incorporate the spec fix of whatwg/dom#1452Fixes #44742
Testing: WPT