starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-04-17 11:41:04 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Sometimes, terminal is not responsive to mouse events #7802

New Issue
Closed
opened 2026-01-31 01:12:59 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 01:12:59 +00:00
Owner
Copy Link

Originally created by @nlguerra2003 on GitHub (Apr 29, 2020).

Once I left the terminal opened for a while, I can notice that the terminal is not responsive to mouse events anymore, and the mouse pointer design keeps on horizontal movement mode (the pointer with two arrows, one to the left, the other to the right).
The mouse is useless in any button of the terminal (since buttons to child windows or alert boxes), though they all work correctly (when key-stroking at least).
I do not think I could give any more details (reproduction, for example), and I did my best to explain the error itself, but if any of you guys think you actually need more information, I will give it to you as well and fast as possible.

Originally created by @nlguerra2003 on GitHub (Apr 29, 2020). Once I left the terminal opened for a while, I can notice that the terminal is not responsive to mouse events anymore, and the mouse pointer design keeps on _horizontal movement_ mode (the pointer with two arrows, one to the left, the other to the right). The mouse is useless in any button of the terminal (since buttons to child windows or alert boxes), though they all work correctly (when key-stroking at least). I do not think I could give any more details (reproduction, for example), and I did my best to explain the error itself, but if any of you guys think you actually need more information, I will give it to you as well and fast as possible.
claunia added the Area-InputResolution-DuplicateProduct-Terminal labels 2026-01-31 01:12:59 +00:00
claunia commented 2026-01-31 01:13:00 +00:00
Author
Owner
Copy Link

@nlguerra2003 commented on GitHub (Apr 29, 2020):

Update: the mouse pointer design is not always the horizontal move one. It varies depending on the border you hover when entering the window (entering from sides will make the cursor a horizontal moving, while entering from below makes it a vertical moving and entering from the status bar, over the window, will make it stay as an arrow pointer unless there is a tab. In that case it will make it an horizontal move cursor).

@nlguerra2003 commented on GitHub (Apr 29, 2020): Update: the mouse pointer design is not always the _horizontal move_ one. It varies depending on the border you hover when entering the window (entering from sides will make the cursor a _horizontal moving_, while entering from below makes it a _vertical moving_ and entering from the status bar, over the window, will make it stay as an _arrow pointer_ unless there is a tab. In that case it will make it an _horizontal move_ cursor).
claunia commented 2026-01-31 01:13:00 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 29, 2020):

@Vyber90 any chance you're using PowerToys?

What version of the Terminal are you running?

@zadjii-msft commented on GitHub (Apr 29, 2020): @Vyber90 any chance you're using PowerToys? What version of the Terminal are you running?
claunia commented 2026-01-31 01:13:00 +00:00
Author
Owner
Copy Link

@nlguerra2003 commented on GitHub (Apr 29, 2020):

@zadjii-msft I use PowerToys, but I do not let it run in the background for performance reasons. Only for PowerRename.
My WT version is 0.11.1121.0

@nlguerra2003 commented on GitHub (Apr 29, 2020): @zadjii-msft I use PowerToys, but I do not let it run in the background for performance reasons. Only for PowerRename. My WT version is 0.11.1121.0
claunia commented 2026-01-31 01:13:00 +00:00
Author
Owner
Copy Link

@ScatteredRay commented on GitHub (May 6, 2020):

I'm actually having the same and persistent problem right now. It is happening on a newly opened terminal, and persists even after opening. For me it's the vertical move drag mouse.

Afaik I am not using PowerToys. I'm running version 0.11.1191.0 distributed from the windows store.

@ScatteredRay commented on GitHub (May 6, 2020): I'm actually having the same and persistent problem right now. It is happening on a newly opened terminal, and persists even after opening. For me it's the vertical move drag mouse. Afaik I am not using PowerToys. I'm running version 0.11.1191.0 distributed from the windows store.
claunia commented 2026-01-31 01:13:01 +00:00
Author
Owner
Copy Link

@ScatteredRay commented on GitHub (May 6, 2020):

I guess an additional difference in my case is the entire terminal seems to be also un-responsive to keyboard input. I can drag the window from the title bar, but none of the title-bar buttons work, nor does right-clicking do anything.

@ScatteredRay commented on GitHub (May 6, 2020): I guess an additional difference in my case is the entire terminal seems to be also un-responsive to keyboard input. I can drag the window from the title bar, but none of the title-bar buttons work, nor does right-clicking do anything.
claunia commented 2026-01-31 01:13:01 +00:00
Author
Owner
Copy Link

@sqeezy commented on GitHub (May 11, 2020):

I have the same problem. The whole window doesn't respond to mouse actions other than dragging via the title bar. Closing power toys and restarting the terminal solves the problem.

@sqeezy commented on GitHub (May 11, 2020): I have the same problem. The whole window doesn't respond to mouse actions other than dragging via the title bar. Closing power toys and restarting the terminal solves the problem.
claunia commented 2026-01-31 01:13:01 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 15, 2020):

@ScatteredRay that sounds like #4448, actually. We're working with the input team to track that one down.

@Vyber90 even though you're not running PowerToys constantly, i'd be interested to see if upgrading it to >=0.17 helps you.

@DHowett-MSFT commented on GitHub (May 15, 2020): @ScatteredRay that sounds like #4448, actually. We're working with the input team to track that one down. @Vyber90 even though you're not running PowerToys constantly, i'd be interested to see if upgrading it to >=0.17 helps you.
claunia commented 2026-01-31 01:13:02 +00:00
Author
Owner
Copy Link

@nlguerra2003 commented on GitHub (May 15, 2020):

@DHowett-MSFT I just observed that, if I do not use PowerToys at all, the Terminal's window works correctly as far as I am concerned. With PT 0.17 it works properly too.

By the way, I am that guy who sent you the diagnostics report about some keyboard problems in order to not make a whole new GitHub issue. Actually, it seems like there were mouse problems in the beginning, but now they got replaced by keyboard troubles.

@nlguerra2003 commented on GitHub (May 15, 2020): @DHowett-MSFT I just observed that, if I do not use PowerToys at all, the Terminal's window works correctly as far as I am concerned. With PT 0.17 it works properly too. By the way, I am that guy who sent you the diagnostics report about some keyboard problems in order to not make a whole new GitHub issue. Actually, it seems like there were mouse problems in the beginning, but now they got replaced by keyboard troubles.
claunia commented 2026-01-31 01:13:02 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 15, 2020):

Thanks for that repro, by the way. The Windows team is, as you might imagine, busy with some conference stuff... but we'll be able to get to it soon.

Thanks for confirming about PT as well. Gonna close this one out as a duplicate of the other issue we're using to track "powertoys blows up terminal".

/dup #3325.

@DHowett-MSFT commented on GitHub (May 15, 2020): Thanks for that repro, by the way. The Windows team is, as you might imagine, busy with some conference stuff... but we'll be able to get to it soon. Thanks for confirming about PT as well. Gonna close this one out as a duplicate of the other issue we're using to track "powertoys blows up terminal". /dup #3325.
claunia commented 2026-01-31 01:13:03 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 15, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (May 15, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Input Product-Terminal Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7802
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?