Resolved the Tab key navigation issue in TextInputLayout #201
Conversation
This file contains hidden or 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
Kamalesh-Periyasamy changed the title 
Choza-rajan approved these changes Jul 2, 2025
bricefriha reviewed Jul 2, 2025
Choza-rajan approved these changes Jul 8, 2025
| /azp run |
| Azure Pipelines successfully started running 1 pipeline(s). |
github-project-automation bot moved this from In Review to Done in MAUI Toolkit Development Board Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Root Cause of the Issue
The use of Opacity = 0 for certain UI elements excluded them from the Tab key navigation hierarchy, as the system did not consider them visible or focusable.
Description of Change
To address this, we introduced a minimal saturation opacity value that keeps elements visually hidden but logically present for accessibility and keyboard navigation. This update ensures the TextInputLayout is included in the focus traversal order via Tab key navigation. The fix applies consistently across supported platforms including macOS (via MacCatalyst), Windows, Android, and iOS, ensuring unified behavior
Issues Fixed
Fixes #178
Screenshots
Before:
BeforeFix-728739-demo.mp4
After:
msedge_55U58VryGi.mp4