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
I noticed that some BorderlessButtons would stop responding to touches on iOS, and investigating, the cause seems to be that disbled accessibility gesture recognizers are being added to certain child views of RNGestureHandlerButton. This in turn causes the child view to return true from shouldHandleTouch, despite this view not having any tappable gesture recognizers.
It looks like a bandaid fix here might be to check for enabled gesture recognizers, rather than checking that the count is greater than zero, so that these strange, untappable, disabled gesture recognizers don't break the parent button's touch handling
Steps to reproduce
Use BorderlessButton with a child view , which in turn has some child view
Update the state of the app, generally just use it, this happens randomly
Observe that some buttons become permanently unable to respond to taps
With the debugger, observe that the affected RNGestureHandlerButton has a child view RCTViewComponentView which has two disabled accessibility gesture recognizers
Description
I noticed that some BorderlessButtons would stop responding to touches on iOS, and investigating, the cause seems to be that disbled accessibility gesture recognizers are being added to certain child views of RNGestureHandlerButton. This in turn causes the child view to return true from shouldHandleTouch, despite this view not having any tappable gesture recognizers.
It looks like a bandaid fix here might be to check for enabled gesture recognizers, rather than checking that the count is greater than zero, so that these strange, untappable, disabled gesture recognizers don't break the parent button's touch handling
Steps to reproduce
Snack or a link to a repository
https://snack.expo.io/
Gesture Handler version
2.21.1
React Native version
0.76.0
Platforms
iOS
JavaScript runtime
None
Workflow
None
Architecture
None
Build type
None
Device
None
Device model
No response
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: