Fix Modal Test using correct Page

[tj-devel709]

Description of Change

After this PR, the Controls.DeviceTest PushingNavigationPageModallyWithShellShowsToolbarCorrectly is failing because FindResponder is being called on the page that is not currently showing. That page's window is null and the test fails because it cannot continue. The fix is to call FindResponder on the page that is showing instead since that window is not null.

[Copilot]

PR Overview

This PR fixes a failing modal test by ensuring that the assertions are performed on the correct page that is visible. The changes replace calls that assert properties on windowPage with assertions on a newly created secondPage.

• Replace anonymous page creation with a named variable for clarity.
• Update assertions to target the visible page after removing the modal page.

Reviewed Changes

File	Description
src/Controls/tests/DeviceTests/Elements/Modal/ModalTests.cs	Updated the test to push a second page and perform assertions on its handler rather than on the windowPage handler

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

Comments suppressed due to low confidence (2)

src/Controls/tests/DeviceTests/Elements/Modal/ModalTests.cs:207

• [nitpick] Using secondPage.Handler instead of windowPage.Handler fixes the issue with null window, but consider adding an inline comment to clarify this reasoning for future maintainers.

await AssertEventually(() => IsNavigationBarVisible(secondPage.Handler));

src/Controls/tests/DeviceTests/Elements/Modal/ModalTests.cs:208

• [nitpick] Similarly, using secondPage.Handler here is the intended fix; an inline comment explaining the context would improve clarity.

await AssertEventually(() => IsBackButtonVisible(secondPage.Handler));