-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Elements unnecessarily re-created when an above v-for changes. #5618
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'm not entirely sure, but this looks like a bug to me, because this only happens with the slot content. |
I just ran into something similar. Although in my example, a Probably related? |
@pengchongfu, Also works if you add a |
Version
2.3.2
Reproduction link
https://jsfiddle.net/gazugafan/a8kverza/2/
Steps to reproduce
Change the inputs marked "Change Me", then add a row. Any inputs following the v-for rows get re-created (and lose their value), while inputs above remain as they are. This only seems to happen when the inputs and v-for element are contained in a parent component's slot.
What is expected?
All inputs remain unchanged--regardless of what happens to the sibling v-for element.
What is actually happening?
Any input elements following the v-for are re-created--resetting their value.
The text was updated successfully, but these errors were encountered: