[Android] Input controls should not change keyboard visibility - UITest #29569
+98
−0
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
There was a problem hiding this comment.
Pull Request Overview
This PR introduces a new UITest for Android to ensure that input controls do not change keyboard visibility unexpectedly.
- Adds a UITest in TestCases.Shared.Tests to validate keyboard visibility after unfocusing input controls
- Updates the host app with corresponding UI components and event handling to support the test
- Ensures automated tests cover the issue described in [Testing] Create Tests for all input based controls that make sure we don't change keyboard behavior #29558
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue29558.cs | Introduces a new UITest verifying keyboard visibility behavior for various input controls |
| src/Controls/tests/TestCases.HostApp/Issues/Issue29558.xaml.cs | Implements the event handler for triggering unfocus on different input controls |
| src/Controls/tests/TestCases.HostApp/Issues/Issue29558.xaml | Provides the UI layout that includes input controls and a button to trigger unfocus |
kubaflo
added
platform/android 🤖
area-controls-entry
|
/azp run MAUI-UITests-public |
|
Azure Pipelines successfully started running 1 pipeline(s). |
jsuarezruiz
requested changes
May 19, 2025
src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue29558.cs
Outdated
Show resolved
Hide resolved
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.
Note
Are you waiting for the changes in this PR to be merged?
It would be very helpful if you could test the resulting artifacts from this PR and let us know in a comment if this change resolves your issue. Thank you!
Issues Fixed
Fixes #29558