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

Unable to detect when key is being held down in crossterm #19650

New Issue
Closed
opened 2026-01-31 06:49:43 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:49:43 +00:00
Owner
Copy Link

Originally created by @lesleyrs on GitHub (Apr 6, 2023).

Windows Terminal version

1.16.10261.0

Windows build number

10.0.19045.0

Other Software

Crossterm crate https://crates.io/crates/crossterm 0.26.1 latest

Steps to reproduce

Crossterm is a terminal library that recently added the ability to detect when a key is being held down and released.

On both conhost and wezterm this works as intended. In the crate if you run cargo run --example event-poll-read in both of these terminals it will correctly show input.

While on windows terminal for keys that produce letters it will just send "released" right after "pressed". Some other keys like arrow keys and tab do work correctly though.

This is not only a lack of functionality but can also create some weird side effects by keys being released unintentionally.

Expected Behavior

Example of conhost correctly registering key presses and only release when released:

image

Actual Behavior

In windows terminal it looks like:

image

Originally created by @lesleyrs on GitHub (Apr 6, 2023). ### Windows Terminal version 1.16.10261.0 ### Windows build number 10.0.19045.0 ### Other Software Crossterm crate https://crates.io/crates/crossterm 0.26.1 latest ### Steps to reproduce Crossterm is a terminal library that recently added the ability to detect when a key is being held down and released. On both conhost and wezterm this works as intended. In the crate if you run `cargo run --example event-poll-read` in both of these terminals it will correctly show input. While on windows terminal for keys that produce letters it will just send "released" right after "pressed". Some other keys like arrow keys and tab do work correctly though. This is not only a lack of functionality but can also create some weird side effects by keys being released unintentionally. ### Expected Behavior Example of conhost correctly registering key presses and only release when released: ![image](https://user-images.githubusercontent.com/19632758/230240057-b55f096a-09d0-443d-8303-f34f707c37cc.png) ### Actual Behavior In windows terminal it looks like: ![image](https://user-images.githubusercontent.com/19632758/230240221-882083ae-3cdd-495e-9390-ce7ad2e37eff.png)
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:49:43 +00:00
claunia commented 2026-01-31 06:49:44 +00:00
Author
Owner
Copy Link

@lesleyrs commented on GitHub (Apr 6, 2023):

Just to be clear it's not just me with this issue, most people using crossterm fixed it by only checking for key press OR release. But that doesn't fix the problem.

@lesleyrs commented on GitHub (Apr 6, 2023): Just to be clear it's not just me with this issue, most people using crossterm fixed it by only checking for key press OR release. But that doesn't fix the problem.
claunia commented 2026-01-31 06:49:44 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 6, 2023):

Hey, thanks for the excellent repro! We're actually tracking this over in /dup #8440, and it's blocked on the Windows input subsystem Terminal is using (it doesn't give us as much fine-grained info as the old Windows Console one). Really sorry about that! Please subscribe over there for updates. 😄

@DHowett commented on GitHub (Apr 6, 2023): Hey, thanks for the excellent repro! We're actually tracking this over in /dup #8440, and it's blocked on the Windows input subsystem Terminal is using (it doesn't give us as much fine-grained info as the old Windows Console one). Really sorry about that! Please subscribe over there for updates. :smile:
claunia commented 2026-01-31 06:49:44 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Apr 6, 2023):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Apr 6, 2023): 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 Issue-Bug 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#19650
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?