Fix InAppMessage Scrolling #640
Merged
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
Problem: Currently, InAppMessages with content overflowing the bounds are not scrollable even when gestures are disabled. This is because the
draggable
effect on the AndroidView that hosts the WebView is conflicting with the WebViews scroll (isHorizontalScrollEnabled
,isVerticalScrollEnabled
).Solution: Apply gesture detection on the frame of the WebView i.e the Card inside the
MessageFrame
and ensure that it is enabled only if gestures are not available.Also fixed deprecated usage of
performGesture
withperformTouchInput
Related Issue
#638
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: