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

VT/xterm mouse reporting not working at all outside of WSL #20489

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

Originally created by @jhmaster2000 on GitHub (Sep 17, 2023).

Windows Terminal version

1.17.11461.0

Windows build number

Microsoft Windows [Version 10.0.19045.3448]

Other Software

PowerShell 7.4.0-preview.5
WSL version: 1.2.5.0

Steps to reproduce

To reproduce the expected behavior inside WSL: echo -e '\E[?1006h' + echo -e '\E[?1003h'

To reproduce the faulty behavior outside WSL: Write-Output "$([char]27)[?1006h" + Write-Output "$([char]27)[?1003h"

Extra info

According to https://github.com/microsoft/terminal/issues/545#issuecomment-509623410, #14958, this article and lots of other sources everything seems to indicate this is supposed to be supported, even outside of WSL according to the last article.

I've already found references of some comments saying "QuickEdit" mode might interfere with VT mouse capture, but I already turned that off and it still doesn't work. I've also already tried the command: Set-ItemProperty HKCU:\Console VirtualTerminalLevel -Type DWORD 1 but I'm pretty sure that was already set anyway.

I can also reproduce this outside of WT with pwsh.exe directly, and have looked through the PowerShell repository issues for this too, but found conflicting cases of people being redirected back and forth between that repository and this one for similar issues to mine (because apparently conhost issues are also tracked here?), so I'm not really sure which one this would fit better, feel free to move the issue to PowerShell if I guessed wrong.

Expected Behavior

Inside WSL, I obtain the following:

jhmaster@Ubuntu:~$ echo -e '\E[?1006h'

jhmaster@Ubuntu:~$ echo -e '\E[?1003h'

jhmaster@Ubuntu:~$ 35;66;17m35;65;17m35;64;17m35;64;16m35;63;16m35;62;16m35;61;16m...

from moving the mouse around after the two inputs. I expected the same feedback outside of WSL.

Actual Behavior

Outside of WSL:

PS C:\...> Write-Output "$([char]27)[?1006h"

PS C:\...> Write-Output "$([char]27)[?1003h"

PS C:\...>

No matter what is done with the mouse, move, drag, click, scroll, etc no feedback is given by the terminal.

Originally created by @jhmaster2000 on GitHub (Sep 17, 2023). ### Windows Terminal version 1.17.11461.0 ### Windows build number Microsoft Windows [Version 10.0.19045.3448] ### Other Software PowerShell 7.4.0-preview.5 WSL version: 1.2.5.0 ### Steps to reproduce To reproduce the *expected* behavior inside WSL: `echo -e '\E[?1006h'` + `echo -e '\E[?1003h'` To reproduce the *faulty* behavior outside WSL: `Write-Output "$([char]27)[?1006h"` + `Write-Output "$([char]27)[?1003h"` ### Extra info According to https://github.com/microsoft/terminal/issues/545#issuecomment-509623410, #14958, [this article](https://www.zdnet.com/article/microsofts-windows-terminal-now-has-mouse-support-for-windows-subsystem-for-linux/) and lots of other sources everything seems to indicate this is supposed to be supported, even outside of WSL according to the last article. I've already found references of some comments saying "QuickEdit" mode might interfere with VT mouse capture, but I already turned that off and it still doesn't work. I've also already tried the command: `Set-ItemProperty HKCU:\Console VirtualTerminalLevel -Type DWORD 1` but I'm pretty sure that was already set anyway. I can also reproduce this outside of WT with pwsh.exe directly, and have looked through the PowerShell repository issues for this too, but found conflicting cases of people being redirected back and forth between that repository and this one for similar issues to mine (because apparently conhost issues are also tracked here?), so I'm not really sure which one this would fit better, feel free to move the issue to PowerShell if I guessed wrong. ### Expected Behavior Inside WSL, I obtain the following: ``` jhmaster@Ubuntu:~$ echo -e '\E[?1006h' jhmaster@Ubuntu:~$ echo -e '\E[?1003h' jhmaster@Ubuntu:~$ 35;66;17m35;65;17m35;64;17m35;64;16m35;63;16m35;62;16m35;61;16m... ``` from moving the mouse around after the two inputs. I expected the same feedback outside of WSL. ### Actual Behavior Outside of WSL: ``` PS C:\...> Write-Output "$([char]27)[?1006h" PS C:\...> Write-Output "$([char]27)[?1003h" PS C:\...> ``` No matter what is done with the mouse, move, drag, click, scroll, etc no feedback is given by the terminal.
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 Issue-Bug Needs-Repro Needs-Tag-Fix Priority-2 Product-Terminal
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#20489
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?