You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Android 9 and Ios 12, nativescript playground and sidekick
Steps to reproduce
open playground app on phone. change a switch and scroll. for example, if you switch off "eight", "eight" might switch back on as you scroll, or other items may switch off.
What is expected?
the model is affected as intended
What is actually happening?
the model is changed unpredictably. As you scroll, the checkedChanged event fires unintentionally.
This is likely due to your virtual scroll implementation. If I need to change my code to make this work I am open to that. But I do not see a workaround right now because the event fires when it should not. I don't know what version the playground uses so I selected the latest version.
The text was updated successfully, but these errors were encountered:
OK I have worked on this a little more and I don't think it has anything to do with the event firing. The listView is actively over-writing changes in the model when you scroll.
Version
2.5.0-alpha.1
Reproduction link
https://play.nativescript.org/?template=play-vue&id=EpO6YJ
Platform and OS info
Android 9 and Ios 12, nativescript playground and sidekick
Steps to reproduce
open playground app on phone. change a switch and scroll. for example, if you switch off "eight", "eight" might switch back on as you scroll, or other items may switch off.
What is expected?
the model is affected as intended
What is actually happening?
the model is changed unpredictably. As you scroll, the checkedChanged event fires unintentionally.
This is likely due to your virtual scroll implementation. If I need to change my code to make this work I am open to that. But I do not see a workaround right now because the event fires when it should not. I don't know what version the playground uses so I selected the latest version.
The text was updated successfully, but these errors were encountered: