microsoft / microsoft/microsoft-ui-xaml
TextBox in ListView hidden behind On-Screen Keyboard
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8.4k
- Forks
- 942
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 105
Description
### Describe the bug
When using a ListView with TextBox items and enabling the On-Screen Keyboard (OSK) setting, focusing on an Entry causes the keyboard to appear, but the focused Entry is hidden behind it. The ListView does not scroll automatically to keep the focused element in view.
### Steps to reproduce the bug
1.Enable OSK setting in Windows.
Enable the touch screen via Windows Settings -> Personalization -> Text Input -> Touch Keyboard and Windows Settings -> Time & Language -> Typing -> Touch Keyboard to always.
2.Use a ListView with Entry/TextBox template.
3.Focus on a lower Entry item — it gets covered by the keyboard.
OR
Deploy the below sample.
[WinUIAppTesting.zip](https://github.com/user-attachments/files/21523459/WinUIAppTesting.zip)
### Expected behavior
The ListView should automatically scroll to ensure the focused Entry is visible above the keyboard.
Actual Behavior:
Focused Entry gets hidden behind the On-Screen Keyboard and is not accessible without manually scrolling.
### Screenshots
https://github.com/user-attachments/assets/acf7a1a1-4d3a-4eb8-b5c3-8c8756c8a626
### NuGet package version
WinUI 3 - Windows App SDK 1.7.3: 1.7.250606001
### Windows version
Windows 11 (24H2): Build 26100
### Additional context
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Run the attached WinUIAppTesting.zip reproduction with the Windows OSK settings described in the issue. Start by observing ListView focus behavior when the keyboard appears; done means a focused lower Entry is automatically scrolled into view above the keyboard.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100