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

[VT Mouse Mode] No mouse tracking when window is unfocused #9067

New Issue
Open
opened 2026-01-31 01:45:09 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 01:45:09 +00:00
Owner
Copy Link

Originally created by @o-sdn-o on GitHub (Jun 16, 2020).

NOTES (@DHowett): gnome-terminal and xterm both emit mouse events when the window is unfocused, even on Windows. Perhaps we need to decide whether to do the same?

Steps to reproduce

Use WSL profile, enable the mouse tracking mode SGR (1006):

echo -e '\e[?1003;1006h'

Unfocus the terminal window.
Mouse movement on the window is no longer tracked when the terminal window loses focus.

Expected behavior

The terminal tracks mouse movement regardless of focus.

Actual behavior

The terminal does not track the mouse when the window is unfocused.

Originally created by @o-sdn-o on GitHub (Jun 16, 2020). **NOTES** (@DHowett): gnome-terminal and xterm both emit mouse events when the window is unfocused, even on Windows. Perhaps we need to decide whether to do the same? --- # Steps to reproduce Use WSL profile, enable the mouse tracking mode `SGR (1006)`: ```cmd echo -e '\e[?1003;1006h' ``` Unfocus the terminal window. Mouse movement on the window is no longer tracked when the terminal window loses focus. # Expected behavior The terminal tracks mouse movement regardless of focus. # Actual behavior The terminal does not track the mouse when the window is unfocused.
claunia added the Product-ConhostIssue-TaskArea-InputArea-VT labels 2026-01-31 01:45:09 +00:00
claunia commented 2026-01-31 01:45:10 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 16, 2020):

I was ready to mark this one "by design," but xterm and gnome-terminal don't agree with me. This may have a follow-on effect for win32 mouse records. Before I commit this task to the backlog, though, I'd like to understand a couple things:

  1. Why would somebody want this?
  2. Should it be user-configurable?

/cc @zadjii-msft, who owned mouse events for conhost before WT and may recall why we didn't pass them through when the window wasn't focused.

@DHowett commented on GitHub (Jun 16, 2020): I was ready to mark this one "by design," but xterm and gnome-terminal don't agree with me. This may have a follow-on effect for _win32 mouse records_. Before I commit this task to the backlog, though, I'd like to understand a couple things: 1. Why would somebody want this? 2. Should it be user-configurable? /cc @zadjii-msft, who owned mouse events for conhost before WT and may recall why we didn't pass them through when the window wasn't focused.
claunia commented 2026-01-31 01:45:10 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 16, 2020):

I honestly don't remember - does conhost get mouse events when it's not focused? I was just turning mouse events into VT, I bet we don't even get them when the console isn't focused.

@zadjii-msft commented on GitHub (Jun 16, 2020): I honestly don't remember - does _conhost_ get mouse events when it's not focused? I was just turning mouse events into VT, I bet we don't even get them when the console isn't focused.
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 Area-VT Issue-Task Product-Conhost
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#9067
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?