Skip to content

fix: [#1803] Fixes issue where the sibling obtained when MutationObserver monitors node removal was null#1805

Merged
capricorn86 merged 2 commits intocapricorn86:masterfrom
uxuip:master
May 27, 2025
Merged

fix: [#1803] Fixes issue where the sibling obtained when MutationObserver monitors node removal was null#1805
capricorn86 merged 2 commits intocapricorn86:masterfrom
uxuip:master

Conversation

@uxuip
Copy link
Copy Markdown
Contributor

@uxuip uxuip commented Apr 17, 2025

Fixes: #1803

The test content is consistent with browser behavior:

image

…utationObserver monitors node removal was null
@uxuip uxuip requested a review from capricorn86 as a code owner April 17, 2025 06:51
capricorn86
capricorn86 previously approved these changes May 27, 2025
Copy link
Copy Markdown
Owner

@capricorn86 capricorn86 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your contribution @uxuip! ⭐

@capricorn86 capricorn86 merged commit 5e830a1 into capricorn86:master May 27, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

When using MutationObserver to observe element removal, previousSibling and nextSibling get a value of null

2 participants