Always extract ancestor handlers on Android #1710
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently handlers attached to the ancestors of a view are extracted only if the view overflows its parent as described in #1618. There is at least one more use-case where that would be a desirable behavior: if the view has
pointer-eventsprop set tobox-nonethen the view itself cannot become the target of touch events but its children can, however currently any gesture handler attached to that view would not be extracted when its child captures a touch event.An example of this can be found in this issue: #1000 (note that this PR does not fully resolve this issue as there are more things to be addressed there).
Test plan
Tested on the Example app and on slightly modified code from the linked issue (imported touchables and flatlist from
react-native-gesture-handlerinstead ofreact-native).