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
changed the title [-]Gesture detector to dismiss keyboard is not working[/-][+]ScrollablePositionedList: Gesture detector to dismiss keyboard is not working[/+]on Apr 16, 2020
Just try a GestureDetector in scrollable_positioned_list and you'll see that it's not working. Something in the package is blocking the children's gesture detector from firing. once in a while, ontap works but rarely, but onLongPress never works.
I found out the my problem was using a UniqueKey() with my stateful widget that made it unable to detect gesturedetector regularly. But the time I figured it out, I had already switch my code to use a Listview.Builder instead SrollablePositionedList so I'm not sure if the issue is specifically tied to your package as well.
Activity
[-]Gesture detector to dismiss keyboard is not working[/-][+]ScrollablePositionedList: Gesture detector to dismiss keyboard is not working[/+]jamesderlin commentedon Apr 16, 2020
It would help a lot if you could provide sample code (ideally a test) that can reproduce the problem. Thanks!
tarobins commentedon Apr 29, 2020
+1 to what @jamesderlin said, but I will try to repo. In this case, I think I understand sufficiently to make an attempt at repoing.
AxesandGrinds commentedon Jun 20, 2020
Just try a GestureDetector in scrollable_positioned_list and you'll see that it's not working. Something in the package is blocking the children's gesture detector from firing. once in a while, ontap works but rarely, but onLongPress never works.
AxesandGrinds commentedon Jun 21, 2020
I found out the my problem was using a UniqueKey() with my stateful widget that made it unable to detect gesturedetector regularly. But the time I figured it out, I had already switch my code to use a Listview.Builder instead SrollablePositionedList so I'm not sure if the issue is specifically tied to your package as well.