Unstable behaviour when used in an iterator like v-for

[salvationarinze]

I use checkbox to show a list of items and whenever I check a box, I remove it from the list. When this operation occurs, the checkbox replaced the previous one in that becomes checked automatically. It causes lots of instability. Please check

[alfausto]

I have a similar issue. I have a checkbox inside a listview with a for. It renders fine, but, whenever I tap some line, this checks others and the action function runs several times... I thought it was my mistake and i've been checking my code for hours... Could someone give us a hand?

[Bobbel0815]

Got a related problem. Inside a v-for, the change of the :checked prop get not registered. I tried to copy the behavior of the radio buttons, so I took a component and gave it a v-for of objects with a "selected" prop on the :checked prop, but I can't change the :checked prop of the other objects.

[Bobbel0815]

Got a related problem. Inside a v-for, the change of the :checked prop get not registered. I tried to copy the behavior of the radio buttons, so I took a component and gave it a v-for of objects with a "selected" prop on the :checked prop, but I can't change the :checked prop of the other objects.

I found a solution for my problem. The ListView uses a concept called view recycling.
So you have to manually refresh the ListView via the refresh() method.