Explicitly set bounds for iOS ScrollView content holder #8002
Conversation
This file contains 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
jfversluis
approved these changes
Jun 14, 2022
jsuarezruiz
approved these changes
Jun 14, 2022
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Eilon
added
the
area-layout
hartez
force-pushed
the
fix-ios-scrollview-hittesting
branch
from
4d94a9c to
9e60841
Compare
|
Azure Pipelines successfully started running 2 pipeline(s). |
Eilon
added
area-controls-scrollview
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 of Change
The content view which holds the content in an iOS ScrollView is getting its Bounds set. So while it lays out and scrolls with no issues, the hit testing thinks it has no size and never propagates gestures to the ScrollView content.
These changes explicitly set the bounds so that gestures will work.