Closed
Conversation
Contributor
Author
|
I'm not a big fan of this solution, I think it may introduce other bugs, but after a lot of tinkering around this proved to be the only working solution. |
Merged
Member
|
Hmm, weird that the detector has the wrong dimensions while its children are sized correctly. Could you check this part to see if the values there seem correct? |
Member
|
Can you change if the issue is still there with #3930 applied? |
Contributor
Author
I'm surprised to report that fixing shadow node problem did not help. It is still broken without the fix in this PR. |
Contributor
Author
|
Superseded by #3942 |
j-piasecki
added a commit
that referenced
this pull request
Feb 2, 2026
## Description Addresses the underlying issue of #3906 The original issue described in the above PR was caused by wrong shadow node dimensions, which were fixed by #3930. After that, the dimensions were good, but the long press was still failing. This was caused by `shouldCancelWhenOutside` checking the dimensions of the detector while the child was moved. This PR changes the logic so that the child's hitbox is checked when using the native detector. This should be enough for iOS, but on Android, further investigation is needed into whether the entire `transformedEvent` should be in the coordinate space of the detector or its child. ## Test plan See #3906 test plan
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The
minDistanceproperty did not work on ios. The reason was that theGestureDetectorview is sometimes getting collapsed so that it bounds are {x: 0, y:0, width:0, height:0}, then the functionisWithinBoundswill always return false. The solution is to check whether the view is collapsed, and if so, get the bounds of its subview instead.Test plan
Tested on the following example,
minDistanceworks!Details