You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains 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
While working on #4162, I discovered some situations where we fail to clear _nextDom meaning we hang on to possibly detached HTMLElements. This fixes a bug in diffChildren so we always clear _nextDom for components/fragments and clears _nextDom in commitRoot since root VNodes don't necessarily go through diffChildren to get cleared.
I've added some code to teardown to run through the VNode tree and verify that _nextDom is null/undefined.
I also found a reference to _nextDom in Suspense. However in all of our tests it is null so I replaced that call to insertBefore(node, null) with a call to appendChild.
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.
While working on #4162, I discovered some situations where we fail to clear
_nextDom
meaning we hang on to possibly detached HTMLElements. This fixes a bug in diffChildren so we always clear_nextDom
for components/fragments and clears_nextDom
incommitRoot
since root VNodes don't necessarily go throughdiffChildren
to get cleared.I've added some code to teardown to run through the VNode tree and verify that
_nextDom
is null/undefined.I also found a reference to
_nextDom
in Suspense. However in all of our tests it is null so I replaced that call toinsertBefore(node, null)
with a call toappendChild
.