dotnet / dotnet/maui

Touch Screen Usage Cancels Out Mouse Functionality in Input Fields and Navigation

Open
#28,476 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-blazor s/needs-attention s/triaged s/verified t/bug
Dominant language
C#
Stars
23.3k
Forks
2k
Avg merge
1d 14h
Merged PRs (30d)
296

Description

Description

When using both touch screen and mouse interchangeably, the mouse functionality is canceled after interacting with the touch screen. After selecting an input field using the touch screen, subsequent mouse attempts to interact with other input fields or navigate to a different page fail. However, resizing the application window or switching to a different program window sometimes restores the functionality partially.

Additional Information:
Issue History: This issue has been present since .NET 6 and continues to occur in subsequent versions.
The portion of time when resizing resolves the issue seems to be around 38%, though inconsistent.
Switching to only touch screen functionality works, but keyboard input might work on some fields, but not others.
Restarting the application temporarily restores mouse functionality after this issue.

Steps to Reproduce

Actual Behavior:
After interacting with the screen via touch screen, the mouse becomes unresponsive:

  • Unable to click into other input fields.
  • Unable to navigate to a different page using the mouse.
  • However, resizing the application window restores proper mouse functionality approximately 38% of the time.
  • Alternatively, switching to a different program's window and returning to the application may resume normal mouse functionality.

Expected Behavior:
The mouse should continue to function seamlessly after using the touch screen:

  • It should allow clicking into other input fields.
  • Page navigation should not be hindered.
  • Resizing the window or switching between windows should not be required to restore functionality.
Link to public reproduction project repository

(https://github.com/CrownVicPI437/MauiTouchIssues)

Version with bug

8.0.40 SR5

Is this a regression from previous behavior?

No, this is something new

Last version that worked well

No Version Has Worked

Affected platforms

Windows

Affected platform versions

NET MAUI (project targeting net8.0-android, net8.0-ios, net8.0-maccatalyst, net8.0-windows10.0.19041.0).

Did you find any workaround?

NO

Relevant log output

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the linked CrownVicPI437/MauiTouchIssues reproduction project on Windows with .NET MAUI 8.0.40 SR5, then reproduce the touch-to-mouse sequence described in this issue. Trace the affected input and navigation behavior in the MAUI Windows target; done means mouse interaction continues working after touch input without resizing or switching windows.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.