Fix HideSoftInputOnTapped Not Working Net9

[SuthiYuvaraj]

Issue Description

When the MainPage is set as the direct window, enabling HideSoftInputOnTapped prevents the keyboard from hiding when tapping on the screen.

Root Cause

The page receives touch input through ResignFirstResponderTouchGestureRecognizer, controlled by the HasNavigatedTo value. This mechanism applies to both UpdateFocusForView and SetHideSoftInputTapped. For a direct ContentPage, HasNavigatedTo remains false but updates to true in SendNavigatingTo when used within NavigationPage. Hence this works fine for the navigation page.

Description of Change

During UpdatePage, when adding the page to the collection, the parent is checked. If it is a direct window, the page is added to the collection. Additionally, the page count is considered for FeatureEnabled and the OnTapped event to handle HideSoftInput.

Issues Fixed

Fixes #26792
Fixes #21681

Tested the behaviour in the following platforms

• Android
• Windows
• iOS
• Mac

Output Screenshot

Before Issue Fix	After Issue Fix
HideSoftBeforeFix.mov	HideSoftAfterFix.mov

[dotnet-policy-service]

Hey there @SuthiYuvaraj! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

Pull Request Overview

This PR fixes issue #26792 by ensuring that the HideSoftInputOnTapped feature works correctly even when a ContentPage is set as the direct window. Key changes include:

• Adding UI test cases in both TestCases.Shared.Tests and TestCases.HostApp.
• Modifying conditionals in HideSoftInputOnTappedChangedManager and its platform-specific implementations to consider pages whose Parent is a Window.
• Updating Android-specific code to align with the new condition.

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue26792.cs	Added test case to verify soft keyboard behavior
src/Controls/tests/TestCases.HostApp/Issues/Issue26792.cs	Updated UI for Issue26792 to support HideSoftInputOnTapped
src/Controls/src/Core/ContentPage/HideSoftInputOnTappedChanged/HideSoftInputOnTappedChangedManager.cs	Updated conditional to check for direct window usage
src/Controls/src/Core/ContentPage/HideSoftInputOnTappedChanged/HideSoftInputOnTappedChangedManager.Android.cs	Updated condition for Android platform-specific handling
src/Controls/src/Core/ContentPage/HideSoftInputOnTappedChanged/HideSoftInputOnTappedChangedManager.Platform.cs	Updated condition in UpdatePage to handle direct window

[rmarinho]

/rebase

[mattleibow]

Just blocking as something is triggering my brain... This HasNavigatedTo property, should it be set to true in this instance?

Almost like if you set Window.Page = somthing, that something is supposed to get auto navigated to?

[mattleibow]

I feel like this PR fixes a symptom of another problem in this PR: #23420

[mattleibow]

Maybe we can land this PR now to get the issue fixed, and then we can fix it properly and remove this workaround? @PureWeen

[mattleibow]

Approving for now as this code is fine based on the current state of the system. However, a better fix is needed which was started in #23420