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 sequences don't work when DECARM is disabled #21029

New Issue
Open
opened 2026-01-31 07:31:07 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 07:31:07 +00:00
Owner
Copy Link

Originally created by @j4james on GitHub (Dec 31, 2023).

Windows Terminal version

1.19.3172.0

Windows build number

10.0.19045.3803

Other Software

Vttest

Steps to reproduce

  1. Open a WSL shell in Windows Terminal.
  2. Run vttest.
  3. Select the Normal Mouse Tracking test (menu 11.8.5.4)
  4. Click somewhere in the terminal window.

Expected Behavior

You should see the mouse escape sequence starting with <27> [ M <32> output near the top of the page, and a 1 output wherever you've clicked.

Actual Behavior

Some of the characters in the mouse sequence are lost, so it starts with <27> <32>, and there is nothing output in the cell where you've clicked.

This is similar to the problem we had with the Device Attribute reports not working in vttest because it disables auto-repeat mode (#14208). But in this case the lost key events are coming from conpty passing the mouse sequences through TerminalInput::HandleKey, so it only affects Windows Terminal.

The fact that the mouse sequences are being treated as keypresses is already questionable, and I think that's likely the cause of #15083, but I also think HandleKey should be capable of accepting a sequence of key events with a 0 virtual key (as a form of input "passthrough"), without DECARM getting in the way.

So my proposed solution is this: before we even check for repeated keys, if we receive a key-down event, and the virtual key code is 0 or VK_PACKET (which serves a similar purpose), then we should immediately return the given UnicodeChar value as the HandleKey output.

Originally created by @j4james on GitHub (Dec 31, 2023). ### Windows Terminal version 1.19.3172.0 ### Windows build number 10.0.19045.3803 ### Other Software Vttest ### Steps to reproduce 1. Open a WSL shell in Windows Terminal. 2. Run `vttest`. 3. Select the _Normal Mouse Tracking_ test (menu 11.8.5.4) 4. Click somewhere in the terminal window. ### Expected Behavior You should see the mouse escape sequence starting with `<27> [ M <32>` output near the top of the page, and a `1` output wherever you've clicked. ### Actual Behavior Some of the characters in the mouse sequence are lost, so it starts with `<27> <32>`, and there is nothing output in the cell where you've clicked. This is similar to the problem we had with the _Device Attribute_ reports not working in vttest because it disables auto-repeat mode (#14208). But in this case the lost key events are coming from conpty passing the mouse sequences through `TerminalInput::HandleKey`, so it only affects Windows Terminal. The fact that the mouse sequences are being treated as keypresses is already questionable, and I think that's likely the cause of #15083, but I also think `HandleKey` should be capable of accepting a sequence of key events with a `0` virtual key (as a form of input "passthrough"), without `DECARM` getting in the way. So my proposed solution is this: before we even check for repeated keys, if we receive a key-down event, and the virtual key code is `0` or `VK_PACKET` (which serves a similar purpose), then we should immediately return the given `UnicodeChar` value as the `HandleKey` output.
claunia added the Help WantedProduct-ConhostIssue-BugIn-PRArea-VTNeeds-Tag-Fix labels 2026-01-31 07:31:07 +00:00
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-VT Help Wanted In-PR Issue-Bug Needs-Tag-Fix 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#21029
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?