Actively reject UiKitView gestures. #25792
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.
flutter/engine#7307 changes the engine side of embedded UIView to only
reject gestures when the framework sends a
rejectGesturemessage, sothat gesture resolution can done after a touch sequence has ended (see
PR description for flutter/engine#7307 for more details).
This change makes the framework send a
rejectGesturemessage to theengine when a UiKitView rejects a gesture.
I'm planning to land this PR before the engine side change, so right now
it swallows the exception thrown if there is no engine implementation
for
rejectGesture(which keeps us with the current behavior). Afterthis change lands I'll land the engine PR, and then clean up the part
that swallows the exception.
#24076