This repository has been archived by the owner on May 1, 2024. It is now read-only.
[Android] Fix context action/tap gesture conflict when tap gesture is on nested view #1154
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 original fix for 46363 handled the case where a TapGesture was added to the top-level control inside of a DataTemplate; unfortunately, it missed the case where a TapGesture was added to a control nested deeper in the DataTemplate's hierarchy. This fix addresses the more general case.
Bugs Fixed
API Changes
None
Behavioral Changes
None
PR Checklist