[BUG] [iOS] Focusing on Entry within Popup results in Layout Issues

[NeilMalcolm]

Is there an existing issue for this?

• [X] I have searched the existing issues

Did you read the "Reporting a bug" section on Contributing file?

• [X] I have read the "Reporting a bug" section on Contributing file: https://github.com/CommunityToolkit/Maui/blob/main/CONTRIBUTING.md#reporting-a-bug

Current Behavior

I see different behaviour based on the platform and based on how the Popup's Content is laid out.

Issue 1:

When focusing on an Entry within a Popup which has a Color defined, the content of the popup is pushed upwards out of bounds.

Issue 2:

When focusing on an Entry within a Popup which has a Transparent Color defined, the popup itself is pushed upwards farther than the prior popup and if large enough will go offscreen.

You can see examples in these recordings, two popups are shown with t

iPad example

https://github.com/user-attachments/assets/010c23bb-a753-4d61-bb40-adb1d7d87c17

iPhone example

https://github.com/user-attachments/assets/90db45c6-c383-400b-a102-8516a4e4e395

Expected Behavior

The popup itself should move upwards above the keyboard but the content should not be forced upwards.

Possibly the popup should take up remaining space available on the screen.

Additionally

Steps To Reproduce

Issue 1

1. Create a popup with the Color property defined (not Colors.Transparent) with an entry inside
2. Show the popup
3. Focus on the entry
4. See the content is pushed upwards

Issue 2

1. Create a popup with the Color property set to Colors.Transparent with an entry inside
2. Show the popup
3. Focus on the entry
4. See the popup itself is pushed upwards further than before and can go off screen

Link to public reproduction project repository

https://github.com/NeilMalcolm/CommunityToolkitEntryIssue

Environment

- .NET MAUI CommunityToolkit: 9.0.3
- OS: iOS 17.2
- .NET MAUI: 8.0.82

Anything else?

I see we had bug #1561 previously which is marked as closed but I still see this issue. I understand we can use the KeyboardAutoManagerScroll for issue 1, but that doesn't resolve issue 2.