Mouse input ignored for new instances #7431

Closed
opened 2026-01-31 01:03:54 +00:00 by claunia · 8 comments
Owner

Originally created by @carlos-zamora on GitHub (Apr 15, 2020).

Environment

Windows build number: 10.0.19608.0
Windows Terminal version (if applicable): 0.11.1043.0

Steps to reproduce

  1. run wt
  2. use the mouse to do anything

Expected behavior

mouse input should go through to the XAML controls (including TermControl).

Actual behavior

No mouse input is accepted.

Originally created by @carlos-zamora on GitHub (Apr 15, 2020). # Environment ```none Windows build number: 10.0.19608.0 Windows Terminal version (if applicable): 0.11.1043.0 ``` # Steps to reproduce 1. run `wt` 2. use the mouse to do anything # Expected behavior mouse input should go through to the XAML controls (including TermControl). # Actual behavior No mouse input is accepted.
Author
Owner

@carlos-zamora commented on GitHub (Apr 15, 2020):

Actually, all new instances are busted. Investigating now. Especially since there's no repro for @zadjii-msft .

@carlos-zamora commented on GitHub (Apr 15, 2020): Actually, all new instances are busted. Investigating now. Especially since there's no repro for @zadjii-msft .
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 17, 2020):

Did you get a repro?

@DHowett-MSFT commented on GitHub (Apr 17, 2020): Did you get a repro?
Author
Owner

@carlos-zamora commented on GitHub (Apr 17, 2020):

Unfortunately no :(. Reported to the input team and they closed the internal bug as no repro. So, it might be an OS issue? Though this only happened with Terminal. And it only happened when it was on the main monitor. Worked perfectly fine on the secondary monitor.

@carlos-zamora commented on GitHub (Apr 17, 2020): Unfortunately no :(. Reported to the input team and they closed the internal bug as no repro. So, it might be an OS issue? Though this _only_ happened with Terminal. And it only happened when it was on the main monitor. Worked perfectly fine on the secondary monitor.
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 17, 2020):

Res no repro, thanks!

@DHowett-MSFT commented on GitHub (Apr 17, 2020): Res no repro, thanks!
Author
Owner

@oplik0 commented on GitHub (Apr 17, 2020):

I could reproduce it consistently on my machine. Mouse input broken only on main monitor. Video evidence (the weird shaking and the dropdown not showing seem to be artifacts from build-in windows recorder. It was made for games after all, but I didn't want to download something else to do it). One interesting thing is that putting it in between two monitors made the half on the secondary one work, but the part still on main monitor was broken. So it's an issue with something only on main display.

However, I think I also found the culprit - PowerToys. Closing this app solves the issue, though relaunching it doesn't start causing it again (perhaps after restart? Will test further soon, but it's too too late in Poland and I prefer sleep to looking for issues with Windows Terminal :). I'd expect that the issue is caused by either FancyZones or Shortcut Guide, as both present some kind of overlay.

@oplik0 commented on GitHub (Apr 17, 2020): I could reproduce it consistently on my machine. Mouse input broken only on main monitor. [Video evidence](https://imgur.com/LQlX0dr) (the weird shaking and the dropdown not showing seem to be artifacts from build-in windows recorder. It was made for games after all, but I didn't want to download something else to do it). One interesting thing is that putting it in between two monitors made the half on the secondary one work, but the part still on main monitor was broken. So it's an issue with something only on main display. However, I think I also found the culprit - PowerToys. Closing this app solves the issue, though relaunching it doesn't start causing it again (perhaps after restart? Will test further soon, but it's too too late in Poland and I prefer sleep to looking for issues with Windows Terminal :). I'd expect that the issue is caused by either FancyZones or Shortcut Guide, as both present some kind of overlay.
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 17, 2020):

Interesting. I think we have an issue on our repo for that one already -- #3325 perhaps?

@DHowett-MSFT commented on GitHub (Apr 17, 2020): Interesting. I think we have an issue on our repo for that one already -- #3325 perhaps?
Author
Owner

@carlos-zamora commented on GitHub (Apr 17, 2020):

For the record, I also had PowerToys running but I did not think about closing it.

@carlos-zamora commented on GitHub (Apr 17, 2020): For the record, I also had PowerToys running but I did not think about closing it.
Author
Owner

@ericbrownz commented on GitHub (Apr 24, 2020):

The same issue when I run tmux.
It seems mouse input works incorrectly after updated to 0.11.

@ericbrownz commented on GitHub (Apr 24, 2020): The same issue when I run `tmux`. It seems mouse input works incorrectly after updated to 0.11.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7431