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

After upgrading to 1.6, mouse input is not working on my primary screen (works on screen 2+3) #12276

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

Originally created by @oocx on GitHub (Jan 29, 2021).

Environment

Windows build number: 10.0.21296.1010
Windows Terminal version (if applicable): 1.6.10272.0

Any other software?

Steps to reproduce

  1. Upgrade to wt 1.6 (I did not see the problem with previous versions)
  2. Use wt on my primary screen -> mouse input does not work
  3. Move wt to screen 2 or 3 -> mouse input works

Expected behavior

Mouse input should work on all screens.

Actual behavior

After upgrading to 1.6, mouse input stopped working when I use wt on my primary screen. It works on screen 2 +3.

This includes interaction with the title bar like clicking on the "close", "maximize", "minimize" buttons, tab selection, new tab and so on, but also interaction with the terminal area like text selection. It just does not accept any mouse input at all.

If I move the terminal to another screen, mouse input works. When I move it back to my primary screen, it stops working. If it is partly on my primary screen and partly on another screen, then only the part that is on screen 2/3 accepts mouse input.

Originally created by @oocx on GitHub (Jan 29, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.21296.1010 Windows Terminal version (if applicable): 1.6.10272.0 Any other software? ``` # Steps to reproduce 1) Upgrade to wt 1.6 (I did not see the problem with previous versions) 2) Use wt on my primary screen -> mouse input does not work 3) Move wt to screen 2 or 3 -> mouse input works # Expected behavior Mouse input should work on all screens. # Actual behavior After upgrading to 1.6, mouse input stopped working when I use wt on my primary screen. It works on screen 2 +3. This includes interaction with the title bar like clicking on the "close", "maximize", "minimize" buttons, tab selection, new tab and so on, but also interaction with the terminal area like text selection. It just does not accept any mouse input at all. If I move the terminal to another screen, mouse input works. When I move it back to my primary screen, it stops working. If it is partly on my primary screen and partly on another screen, then only the part that is on screen 2/3 accepts mouse input.
claunia added the Resolution-Duplicate label 2026-01-31 03:10:59 +00:00
claunia commented 2026-01-31 03:11:00 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 29, 2021):

Do you have PowerToys installed?

@zadjii-msft commented on GitHub (Jan 29, 2021): Do you have PowerToys installed?
claunia commented 2026-01-31 03:11:00 +00:00
Author
Owner
Copy Link

@oocx commented on GitHub (Jan 29, 2021):

Yes, PowerToys 0.16.1.0

Quitting PowerToys fixes the problem. Thanks! :)

Is this a PowerToys or a WT Bug? If it is a PowerToys Bug, I would open an issue in the PT repo.

@oocx commented on GitHub (Jan 29, 2021): Yes, PowerToys 0.16.1.0 Quitting PowerToys fixes the problem. Thanks! :) Is this a PowerToys or a WT Bug? If it is a PowerToys Bug, I would open an issue in the PT repo.
claunia commented 2026-01-31 03:11:01 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 29, 2021):

Thanks for confirming. I'm pretty sure it's a Powertoys bug. We're tracking this in #6120, #3325, and

I haven't heard any reports of this on newer PowerToys versions. Thanks for sharing the version too - I think you'll probably never see this again if you update PowerToys.

/dup #3325

@zadjii-msft commented on GitHub (Jan 29, 2021): Thanks for confirming. I'm _pretty sure_ it's a Powertoys bug. We're tracking this in #6120, #3325, and * microsoft/PowerToys#4360 * microsoft/PowerToys#3833 * microsoft/PowerToys#3250 * microsoft/PowerToys#3090 I haven't heard any reports of this on newer PowerToys versions. Thanks for sharing the version too - I think you'll probably never see this again if you update PowerToys. /dup #3325
claunia commented 2026-01-31 03:11:01 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 29, 2021):

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 (Jan 29, 2021): 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 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#12276
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?