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

Using SetConsoleMode to set/clear ENABLE_MOUSE_INPUT does not take effect (unless a WriteConsoleW call occurs as well) #20235

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

Originally created by @chrisant996 on GitHub (Jul 14, 2023).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version

1.18.1462.0

Windows build number

10.0.19045.3208

Other Software

I've provided a minimal standalone repro here to eliminate dependencies on anything other than Terminal.
But for completeness: this was discovered in the context of Clink.

Steps to reproduce

This is a regression in 1.18; the problem does not exist in 1.17 and earlier.

Minimal repro program is available at https://github.com/chrisant996/repro_enable_mouse_input.
The repo also includes a pre-built code-signed Repro.exe executable.

See the Readme.md file in that repo for full details and repro instructions.

  1. Start Windows Terminal 1.18
  2. Run the Repro.exe program from the repro_enable_mouse_input repo (you can build it yourself from the sources, or you can run the pre-built code-signed copy)
  3. Move the mouse over the terminal window; you should see no output
  4. Click the primary mouse button on the terminal window; you should see no output
  5. Hold Ctrl+Alt and move the mouse or click the mouse button

Expected Behavior

  • You should see output acknowledging that ReadConsoleInputW received mouse input records.

Actual Behavior

  • Terminal 1.18 -- there is no output (incorrect behavior).
  • Terminal 1.17 -- the output reports received mouse input records (correct behavior).
Originally created by @chrisant996 on GitHub (Jul 14, 2023). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version 1.18.1462.0 ### Windows build number 10.0.19045.3208 ### Other Software I've provided a minimal standalone repro here to eliminate dependencies on anything other than Terminal. But for completeness: this was discovered in the context of [Clink](https://github.com/chrisant996/clink). ### Steps to reproduce This is a regression in 1.18; the problem does not exist in 1.17 and earlier. Minimal repro program is available at https://github.com/chrisant996/repro_enable_mouse_input. The repo also includes a pre-built code-signed `Repro.exe` executable. **See the Readme.md file in that repo for full details and repro instructions.** 1. Start Windows Terminal 1.18 2. Run the `Repro.exe` program from the [repro_enable_mouse_input](https://github.com/chrisant996/repro_enable_mouse_input) repo (you can build it yourself from the sources, or you can run the pre-built code-signed copy) 3. Move the mouse over the terminal window; you should see no output 4. Click the primary mouse button on the terminal window; you should see no output 5. Hold <kbd>Ctrl</kbd>+<kbd>Alt</kbd> and move the mouse or click the mouse button ### Expected Behavior - You should see output acknowledging that ReadConsoleInputW received mouse input records. ### Actual Behavior - Terminal 1.18 -- there is no output (incorrect behavior). - Terminal 1.17 -- the output reports received mouse input records (correct behavior).
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-Server Area-VT In-PR Issue-Bug Needs-Tag-Fix Priority-1 Product-Conpty Severity-Blocking
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#20235
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?