[iOS] Fixed an issue where an Editor with a small height inside a ScrollView would cause the entire page to scroll

[Tamilarasan-Paranthaman]

Root Cause of the issue

• The issue occurred because cursorRect.Bottom was used instead of cursorRect.Y when determining whether the cursor was outside the visible area of the UITextView.

• With a small editor height, the cursor's bottom edge extended beyond the visible area, incorrectly meeting the condition and triggering scrolling. This led to the move value being calculated based on the parent ScrollView, causing unnecessary scrolling.

• Previously, cursorRect.Y was used instead of cursorRect.Bottom, but a recent PR modified this behavior, introducing a regression in .NET 9.

Description of Change

• I have replaced cursorRect.Bottom with cursorRect.Y, restoring the original logic from before the regression. To check if the cursor is outside, I believe we can use cursorRect.Y because it is also meaningful in this context. This fix resolves the reported issue by ensuring that scrolling only occurs when the cursor is completely out of view, preventing unnecessary movement.

Issues Fixed

Fixes #27750

Tested the behaviour in the following platforms

• iOS
• Android
• Windows
• Mac

Screenshot

Before Issue Fix	After Issue Fix
Before-Fix.mov	After-Fix.mov

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Copilot]

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

Comments suppressed due to low confidence (1)

src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue27750.cs:1

• The file contains a BOM (Byte Order Mark) character at the beginning, which should be removed.

using NUnit.Framework;

[jsuarezruiz]

/rebase

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[jsuarezruiz]

/rebase

[jsuarezruiz]

/rebase

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[jsuarezruiz]

/rebase

[jsuarezruiz]

/rebase

[jsuarezruiz]

/azp run MAUI-UITests-public

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.sh | bash -s -- 27948

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.ps1) } 27948"

[StephaneDelcroix]

✅ Approved

The fix is correct and safe to merge.

Analysis Summary

The single-line change from cursorRect.Bottom to cursorRect.Y at line 452 of KeyboardAutoManagerScroll.cs correctly fixes the regression where small-height Editors inside ScrollViews triggered unnecessary page scrolling.

Why This Is Safe

1. Semantically correct: Using cursorRect.Y only triggers scrolling when the cursor's TOP is at/below the view's bottom (completely out of view), preventing false positives for small Editors

2. No regression on PR #24589 scenarios: The Issue19214 tests (cursor stays above keyboard while typing) are handled by ApplyContentInset() - a completely separate code path unaffected by this change

3. Good test coverage: Includes UI test with screenshots for all platforms

4. Minimal, focused change: Single line fix that directly addresses the root cause

LGTM! 🚀

[sheiksyedm]

/rebase