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
We noticed that in RN, onShouldBlockNativeResponder does NOT have any effect on iOS. This is also mentioned in RN documentation. However, when a RN View is used inside RNGestureHandler, returning true in onShouldBlockNativeResponder DOES have an effect on iOS. This difference between RN and RNGestureHandler caused a bit of confusion and should probably be documented.
Upon investigating further, it looks like RNGestureHandler is replacing RN setJSResponderhere with its own. Are there other differences in behaviors because of that? I think all these differences should be documented
Could you provide a snack or a link to a GitHub repository under your username that reproduces the problem?
thomasttvo
changed the title
Confusing behavior of react-native JS responder needs to be documented
Confusing behavior of RN responder when used with RNGestureHandler needs to be documented
Oct 10, 2023
Description
We noticed that in RN,
onShouldBlockNativeResponder
does NOT have any effect on iOS. This is also mentioned in RN documentation. However, when a RN View is used inside RNGestureHandler, returningtrue
inonShouldBlockNativeResponder
DOES have an effect on iOS. This difference between RN and RNGestureHandler caused a bit of confusion and should probably be documented.Upon investigating further, it looks like
RNGestureHandler
is replacing RNsetJSResponder
here with its own. Are there other differences in behaviors because of that? I think all these differences should be documentedUpdate: Looks like the Meta team said replacing
setJSResponder
is "guaranteed to break in the new architecture"Gesture Handler version
2.11.0
React Native version
0.71
Platforms
iOS
JavaScript runtime
Hermes
Workflow
non-expo
Architecture
New
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: