Tabs: fix infinite loop call update when pane destroy #17380
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.
Please make sure these boxes are checked before submitting your PR, thank you!
dev
branch.Issue
Close #16746
Related pr #14496
Desc
paneSlots
matchedcomponentInstance._isDestroyed
instance, and then force update it, so it infinite loop callupdate
.add condition
... && !componentInstance._isDestroyed
in the filter can fix it, but i do not think it is necessary to update allpanes
if onepane
changed.