dotnet / dotnet/maui

Scaled Editor is behind the keyboard on Android

Open
#29,522 6 comments 0 reactions 0 assignees View on GitHub
area-controls-editor area-keyboard has-workaround platform/android s/triaged s/verified t/bug
Dominant language
C#
Stars
23.3k
Forks
2k
Avg merge
1d 14h
Merged PRs (30d)
296

Description

### Description

Hi all,

We use a scalable AbsoluteLayout for accessibility reasons. Our users can zoom any view freely. From MAUI version 7.0.x to version 9.0.40 this worked fine.

![Image](https://github.com/user-attachments/assets/8da37f92-38a6-4730-b9d7-4fb7f0209ac1)

MAUI 9.0.40

From MAUI version 9.0.50 on, an active Editor is not above the keyboard anymore, but behind the keyboard.

![Image](https://github.com/user-attachments/assets/50f1a382-20b4-41a8-88ab-355faef9332a)

MAUI 9.0.70

Please see the attached screenshots. How can we get the previous behaviour back?

I'm sorry, I can’t provide a repository because of company policy. But I’ve attached a sample.

[Sample.zip](https://github.com/user-attachments/files/20228299/Sample.zip)

Thanks for help.

### Steps to Reproduce

Please run the attached sample.

### Link to public reproduction project repository

_No response_

### Version with bug

9.0.70 SR7

### Is this a regression from previous behavior?

Yes, this used to work in .NET MAUI

### Last version that worked well

9.0.40 SR4

### Affected platforms

Android

### Affected platform versions

_No response_

### Did you find any workaround?

_No response_

### Relevant log output

```shell

```

Contributor guide

Open the contributing guide

Research direction

Run the attached Sample.zip on Android with .NET MAUI 9.0.70 SR7 and compare the active Editor's position relative to the keyboard with 9.0.40 SR4. Investigate the regression in the sample's scalable AbsoluteLayout behavior; done means the Editor is again displayed above the keyboard when active.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, csharp
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.