-
-
Notifications
You must be signed in to change notification settings - Fork 8k
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
v-for ref behaves differently under production and development #6697
Comments
Sorry, missclicked |
Edit: the comment I responded to was deleted |
I also think is a bug, the Model can not match View |
I also think this is a bug. When the list changes and the update is triggered, toDisplayString will be called. At this time, the dom has not changed, so the itemRefs value is still 3 divs, and then the converted string is the same as before the update. When comparing dynamicchildren , no updates were made. Also I found that this problem also exists in production mode if the setup syntactic sugar is not used. |
With the composition API it does not work either in production or development. See here |
As a temporary fix, you can create a watcher on the list, then
|
Isn't this a bug? @LinusBorg |
…en prod and dev (vuejs#6714) fix vuejs#6697
…en prod and dev (vuejs#6714) fix vuejs#6697
Vue version
3.2.29
Link to minimal reproduction
https://sfc.vuejs.org/#__DEV__eNp9Uj1v2zAQ/SsHLpYBiXTiqa4cpEOHAu3SteygSmeXLb9AUsog6L/nSMWJkwBZhPt67/HuaWZfvOfTiOzA2tgH5RNETKMH3dnzUbIUJbuTVhnvQoIZAp5qcPaHG23CoYbeGT+WaMIQlbOwwCk4Axsi3Ugrbe9sTKAVfY4ZXv26qeG2hv3v7UtbJTQ/8RQvI2vvWaeqtnC8g1lagMH1o0GbeDcMXycKvhM1WgzVxjtF02FwD3ZTwxUGij6fOj0ij16rHqtdfbP9nJsLaUHe+lsG08y1GtCGNjqNXLtzdXnmylRwCy2z2+0ozjytWI9IJ6OEpr3uElIGMM8X9LLkvB11qVOkFUzNyQW6d54BZct7JcvHeCpmYLEiIzJbuRmsXMQhtCrNVhTeVjyLs5qt9jWm8/xfdJbMLssRc2kQ8eGyrmRkXM4l+5uSjwchRuv/nzk5Le6pJwJZogw2gzP3e37L95/EQK+9rnOMpvkT3EPEQIqS1Vfkgor0szQB7YABw4dib2ZfCb7pvRMt9pAvbHkEVNz6nA==
Steps to reproduce
What is expected?
On each click one element is removed from the list. The itemRefs variable should also be updated with the corresponding number of elements
What is actually happening?
Under production everything works as expected, under development the ref array is "lagging" behind. After one click, the list has 2 elements and the ref array still 3. After a second click, the list has 1 element and the ref array has now 2.
System Info
No response
Any additional comments?
Every 2 seconds the itemRefs variable is printed on the console. There you can see that it is actually updated correctly after each click (in both dev and prod scenarios)
The text was updated successfully, but these errors were encountered: