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
(A video would make this easy to understand, but it's not easy for me to capture one at this second.)
To repro:
Open Flutter Gallery on iOS
Fling scroll on the home page.
Stop the fling with your finger (notice how it starts a splash effect on the item below your finger).
Lift your finger after stopping. Notice that it counted your "stop scroll" as an action and activated the list item below your finger and took you to whatever demo you happened to be over.
Compare this behavior with how flings of other scrolling lists work on iOS (such as Settings), notice that Flutter's behavior is incorrect.
It's possible our behavior here is wrong on Android too, but I haven't confirmed yet.
Thanks to @goderbauer for bringing this to my attention.
Got reverted due to blocking touches even after you stopped scrolling sometimes. Eventually touches would work again, but sometimes took several seconds. I was testing on iOS.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
eseidelGoogle commentedon Aug 4, 2016
We just tested, Android doesn't count these as touches either. @Hixie said he'd take a look.
eseidelGoogle commentedon Aug 5, 2016
Got reverted due to blocking touches even after you stopped scrolling sometimes. Eventually touches would work again, but sometimes took several seconds. I was testing on iOS.
[-]Stopping flings on iOS should not count as a touch[/-][+]Stopping flings should not count as a touch[/+]Roll engine to 0c09bf0.
Roll engine to 0c09bf0. (#16668)
Roll engine to 0c09bf0. (flutter#16668)
github-actions commentedon Sep 6, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.