Skip to content

Resolved the Tab key navigation issue in TextInputLayout #201

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Kamalesh-Periyasamy
Copy link
Contributor

@Kamalesh-Periyasamy Kamalesh-Periyasamy commented Jun 24, 2025

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

@Kamalesh-Periyasamy Kamalesh-Periyasamy changed the title MAUI Resolved the Tab key navigation issue for TextInputLayout across platforms Resolved the Tab key navigation issue in TextInputLayout Jun 24, 2025
@PaulAndersonS PaulAndersonS added this to the v1.0.6 milestone Jun 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

2 participants