[Infrastructure] Fix widget tester tapping on block component (Resolves #2197) #2207
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.
[Infrastructure] Fix widget tester tapping on block component. Resolves #2197
Trying to tap on the downstream position of a block component is always resulting in an upstream selection.
The issue is that the computation to determine the offset to tap relies on
getRectForPosition
. For block components, this always return a rect of the entire component, as is documented in the method:This PR changes the
tapAtDocumentPosition
to handle block components differently, by computing its edge position and returning aRect
of half of the component's width.