Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WinUI Ignores Hide Pointer While Typing Option #9318

Open
aquinn39 opened this issue Feb 6, 2024 · 1 comment
Open

WinUI Ignores Hide Pointer While Typing Option #9318

aquinn39 opened this issue Feb 6, 2024 · 1 comment
Labels
area-Pointer bug Something isn't working team-CompInput Issue for IXP (Composition, Input) team

Comments

@aquinn39
Copy link

aquinn39 commented Feb 6, 2024

Describe the bug

Windows has an option in Settings -> Bluetooth & devices -> Mouse -> Additional mouse settings -> Pointer Options called 'Hide pointer while typing' which is on by default and automatically hides the mouse cursor while you're typing. This is quite useful as sometimes you might click into a text field and start typing and some of the text gets covered by the mouse cursor, so you might need to move the cursor so you can see what you're typing. It isn't a big deal to have to do that, but it can get annoying having to do it a lot. Currently, WPF, Windows Forms, and the Windows common controls already support this feature by default.

Steps to reproduce the bug

  1. Create a WinUI 2 or 3 application
  2. Add a TextBox to the UI
  3. Positon the mouse cursor so that it is over the window with the TextBox
  4. Run the app and type into the TextBox
  5. The cursor does not dissapear, even if it is covering the TextBox

Expected behavior

The cursor should dissapear if it is over the window when typing into the TextBox, as it does when typing into a WPF, Windows Forms or Windows Common Controls TextBox.

Screenshots

This is the option which I am referring to:
image

NuGet package version

WinUI 3 - Windows App SDK 1.4.4: 1.4.231219000

Windows version

Windows 11 (22H2): Build 22621

Additional context

Happens in both WinUI 2 and 3. Also happens on Windows 10 22H2 (Build 19045) and probably all other versions of Windows 11 and 10, but haven't tested other versions.

@aquinn39 aquinn39 added the bug Something isn't working label Feb 6, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the needs-triage Issue needs to be triaged by the area owners label Feb 6, 2024
@HO-COOH
Copy link

HO-COOH commented Feb 7, 2024

Don't really remember this feature. It seems old tech would do this properly, but many of todays' new app does not, like chrome/Edge/all the electron-based app. But interestingly, the new terminal does it while old conhost does not. Would like to know how this is implemented.

@codendone codendone added team-CompInput Issue for IXP (Composition, Input) team area-Pointer and removed needs-triage Issue needs to be triaged by the area owners labels Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Pointer bug Something isn't working team-CompInput Issue for IXP (Composition, Input) team
Projects
None yet
Development

No branches or pull requests

3 participants