Fix incorrect DOM order with conditional ContextProvider and inner keys by JoviDeCroock · Pull Request #5067 · preactjs/preact (original) (raw)
…ys (#5065)
When a VNode is moved via INSERT_VNODE during diffChildren, its old _dom pointer becomes a stale positional reference. Nested diffs that call getDomSibling would traverse the old VNode tree and find this stale _dom, causing subsequent DOM insertions at the wrong position.
Clear the old VNode's _dom after insert so getDomSibling skips moved VNodes and finds the correct insertion point.
JoviDeCroock deleted the fix/5065-dom-order-context-provider-keys branch
rschristian linked an issue
that may beclosed by this pull request
JoviDeCroock added a commit that referenced this pull request
When a VNode is moved via INSERT_VNODE during diffChildren, its old _dom pointer becomes a stale positional reference. Nested diffs that call getDomSibling would traverse the old VNode tree and find this stale _dom, causing subsequent DOM insertions at the wrong position.
Clear the old VNode's _dom after insert so getDomSibling skips moved VNodes and finds the correct insertion point.
Create a unique event-clock for each Preact instance on a page. (#5068)
Fix migrations when we have defaultValue or value on a textarea (#5081)
Add CODEOWNERS for GitHub configuration (#5088)
chore: remove unused Fragment import in forwardported test
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
[ Show hidden characters]({{ revealButtonHref }})