[Android] TouchBehavior prevents keyboard Tab navigation to next element - fix #2673
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
e.Handled = false;
is essential here because it preserves native focus navigation. Without it, your behavior unintentionally blocks keyboard input from reaching other controls or triggering system logic.This subtle line prevents your TouchBehavior from hijacking the keyboard navigation experience — especially important on Android where keyboard interactions are more commonly used with physical keyboards or accessibility tools.
Linked Issues
PR Checklist
approved
(bug) orChampioned
(feature/proposal)main
at time of PRScreen.Recording.2025-05-26.at.20.00.21.mov
Screen.Recording.2025-05-26.at.19.58.19.mov