fix: #10192 When passing a Vnode to the 'is' prop of a <component>, the page does not refresh upon changes in the Vnode #10193
Conversation
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
|
I think this may be a duplicate of #8304. |
|
I believe this problem has been fixed as of 3.4.28. |
|
Thanks for this PR. |
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.
This is a proposal I submitted for bug #10192.
在 minimal reproduction中
The VNode generated by the slot possesses a pathFlag value of 1（TEXT）, which, when subjected to a bitwise OR operation with PatchFlags.BAIL (-2), yields PatchFlags.HOISTED (-1). As a consequence, this results in the diff process omitting the update of the VDom. I am uncertain as to the rationale behind employing a bitwise OR operation in this context and am eager to learn if there exists a superior alternative solution.