No, that forum has been in readonly mode for a while now. You should update your github template here.
So I originally posted this issue here: https://github.com/telerik/nativescript-ui-feedback/issues/351#issuecomment-452815812 but I'm thinking it's better to post it here.
- When you're scrolling through a list supporting
swipeActions, and quickly swipe to the side (while it's still scrolling), the swipe action events will not trigger afterwards. The swipe panel still slides to both sides, but the buttons do nothing (the tap event is ignored). The only way to get them working again is to click the item itself, reopen the slide and re-click the buttons.If you allow the scroll animation to completely settle before trying to swipe, then everything works as expected, but our users aren't that patient.
- When hitting the above bug, the
scrollEndedevent no longer triggers (assume it gets blocked).Both combined, these bugs cause mayhem for us. :-)
We spent the entire day debugging this.We've confirmed that by rolling back to 5.0.1, everything works as expected.
Here's a playground that shows everything working; https://play.nativescript.org/?template=play-ng&id=ne9nN3&v=6 (Playground is running v5.0.1 still)
To see the bugs in action, download the Playground project, and updatenativescript-ui-listviewto 5.1.0.
Then do what I explained above. With the above playground project, we can replicate the problem with 100% consistency.
Android
See above
Playground link plus instructions above
HI @larssn,
I reviewed the provided sample project on my side, however, was unable to recreate the issue. For your convenience, I am attaching video, which demonstrates the behaviour on my side. Please, review the video and check if I am missing something.
demo.zip
Did you remember to update the dependency to 5.1.0?
And if so, are you using an emulator? If it's a race condition you might need a slower device to get the problem to show itself.
Lars
Hi @larssn,
Thank you for your report, we will soon release a fix for the observed issue.
You're very welcome.
Thanks for confirming
Most helpful comment
Hi @larssn,
Thank you for your report, we will soon release a fix for the observed issue.