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

Mouse pointer "vanishes" when moved over Terminal Window #18335

Open
inoperable opened this issue Dec 17, 2024 · 15 comments · May be fixed by #18345
Open

Mouse pointer "vanishes" when moved over Terminal Window #18335

inoperable opened this issue Dec 17, 2024 · 15 comments · May be fixed by #18345
Assignees
Labels
Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) In-PR This issue has a related PR Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-1 A description (P1) Product-Terminal The new Windows Terminal.

Comments

@inoperable
Copy link

          📝where'd this go

Originally posted by @zadjii-msft in #18215 (comment)

Probably this

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Dec 17, 2024
@zadjii-msft
Copy link
Member

@inoperable Could you add any more details/? That PR merged literally 5 days ago, I'm not sure it's even in a canary build currently

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Dec 17, 2024
@inoperable
Copy link
Author

At some point the mouse pointer vanishes permanently after alt tab, I'm not sure what triggers it though. When restarting the terminal it seems fine for a while and then it start again.

It's weird, I thought it's because software rendering first, but nope,also toggled some other settings but I can't figure out when exactly it decides I don't need a mouse pointer shown at all.

Will update if I can pinpoint it more

Drives me nuts

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Dec 17, 2024
@inoperable
Copy link
Author

It trigger must be in some onmouseover event handling on terminal window, not over the tab strip or borders (if that's of sny help). I'll get back to once I got more

@zadjii-msft
Copy link
Member

zadjii-msft commented Dec 17, 2024

This is behavior that's on-by-default for most text fields in Windows. When you start typing in a text input, the cursor vanishes.

Can you check if this setting is on: (just searching for "Pointer" should get you there)
Image

Image

@zadjii-msft zadjii-msft added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Attention The core contributors need to come back around and look at this ASAP. labels Dec 17, 2024
@lhecker
Copy link
Member

lhecker commented Dec 17, 2024

Oh, and please confirm with us what exact version(-number) of Windows Terminal you're using. 🙂

@inoperable
Copy link
Author

inoperable commented Dec 17, 2024

It's not the behavior intended, I'm very sure about it, the is setting OS mouse settings is a good point to eliminate culprits - but it's not it.
What happens is that the pointer gets hidden all the time once the terminal window is in focus and the mouse pointer hovers over it. I can see settings buttons highlighting (as per on mouse over event) but no mouse pointer.

Term is 1.23.241213001-llm, OS 27764.1000 & 19045.4651

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Dec 17, 2024
@inoperable
Copy link
Author

And this seems to be only a 27xxx insiders build exklusive, since I can't replicate it with 19045.xxxx

o.O - so I guess I just wasted your time unnecessary...

@inoperable
Copy link
Author

It's definitely a insiders build exclusive, I couldn't replicate the same on 19045.4651. I apologize for confusions therefore, maybe this is not entirely a waste of time since this might make a come back agai, I'll fiddle around with the insiders build again and will update this thread once I know more when/how

@lhecker
Copy link
Member

lhecker commented Dec 17, 2024

It's possible that this is a bug across any Windows 11 version, because I did struggle quite a bit with making cursor hiding work right. The problem is that the WinUI APIs for doing so are just kind of bad and not very robust. It would not surprise me if they broke between Windows versions.

@lhecker
Copy link
Member

lhecker commented Dec 18, 2024

Leading theory: The current cursor that we get from the WinUI API is non-null but also hidden. This means that when we restore it, we restore a hidden cursor that won't ever go away, because nothing explicitly sets a visible cursor in our code either. Ideally, WinUI would have a cursor stack that you can push/pop into, but in the absence of that we'll just do the next best thing:

@lhecker lhecker self-assigned this Dec 18, 2024
@lhecker lhecker added Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Product-Terminal The new Windows Terminal. Priority-1 A description (P1) Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements labels Dec 18, 2024
@lhecker lhecker added this to the Terminal v1.23 milestone Dec 18, 2024
@inoperable
Copy link
Author

inoperable commented Dec 18, 2024

Hello Again, it actually happens again on Win10 and Win11, I caught the bug after a while in Win10 as well. I cant figure out though when/how its triggered.

Image
No mouse pointer, but the mouse hovers over the button and it reacts with highlighting

Image
Here the same thing, this happens in settiings and in terminal window

@inoperable
Copy link
Author

Image
Invisible Mouse™

@inoperable
Copy link
Author

So, to clarify @lhecker I think you are right, and have it figured out (as mentioned above)

@Zeroes1
Copy link

Zeroes1 commented Dec 19, 2024

@lhecker , @zadjii-msft

I have another problem (but with cursor of mouse too)

i see this since begin use Windows Terminal terminal-1.17.11461.0 to latest canary release

i see this effect only when use WinSSHTerm + Putty
[https://winsshterm.blogspot.com, https://www.putty.org]

when Alt-Tab from window (WinSSHTerm + Putty) to Windows Terminal window, the mouse cursor set to OS BUSY mode.

No effect when returning from other program. No effect when returning to another window (not WT window).

problem reproduction 100%
open NEW issue for this?
https://github.com/user-attachments/assets/b0170e74-ba67-4323-9244-b766cb9bbe71

@lhecker
Copy link
Member

lhecker commented Dec 19, 2024

Yes, I think that's a separate issue.

@lhecker lhecker linked a pull request Dec 20, 2024 that will close this issue
@microsoft-github-policy-service microsoft-github-policy-service bot added the In-PR This issue has a related PR label Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) In-PR This issue has a related PR Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-1 A description (P1) Product-Terminal The new Windows Terminal.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants