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

Opening quakeMode via shortcut/touchpad gesture messes with input / caps lock stuck #19878

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

Originally created by @jonaskuske on GitHub (May 15, 2023).

Windows Terminal version

1.16.10262.0

Windows build number

10.0.22621.0

Other Software

No response

Steps to reproduce

  1. Map 4-finger tap to ctrl+shift+alt+t in Windows Settings
  2. Map ctrl+shift+alt+t to action quakeMode in Terminal settings
  3. Open and close quake window using 4 finger taps

Happens to me both with PowerShell and WSL+zsh, so I don't think it's shell related. I'm using the oh-my-posh prompt in both though, so that is something both shells have in common

Expected Behavior

Opening or closing the window should not change input behavior

Actual Behavior

Sometimes after opening the quakeMode window using a 4-finger tap, I can only input uppercase letters (and pressing the capslock key changes nothing). The behavior of arrow keys is changed, too. The input behavior is stuck and the Terminal basically unusable.

Then, I have to open and close the window a few times using the 4-finger tap until suddenly the input behavior is normal again, seemingly randomly. I haven't found another way to switch to normal input behavior again, leading to a weird open-close dance every time this happens.

I've not yet tried if the same happens with out the touchpad gesture, just using the shortcut. Will update later.

Originally created by @jonaskuske on GitHub (May 15, 2023). ### Windows Terminal version 1.16.10262.0 ### Windows build number 10.0.22621.0 ### Other Software _No response_ ### Steps to reproduce 1. Map 4-finger tap to `ctrl+shift+alt+t` in Windows Settings 2. Map `ctrl+shift+alt+t` to action `quakeMode` in Terminal settings 3. Open and close quake window using 4 finger taps Happens to me both with PowerShell and WSL+zsh, so I don't think it's shell related. I'm using the oh-my-posh prompt in both though, so that is something both shells have in common ### Expected Behavior Opening or closing the window should not change input behavior ### Actual Behavior Sometimes after opening the quakeMode window using a 4-finger tap, I can only input uppercase letters (and pressing the capslock key changes nothing). The behavior of arrow keys is changed, too. The input behavior is stuck and the Terminal basically unusable. Then, I have to open and close the window a few times using the 4-finger tap until suddenly the input behavior is normal again, seemingly randomly. I haven't found another way to switch to normal input behavior again, leading to a weird open-close dance every time this happens. I've not yet tried if the same happens with out the touchpad gesture, just using the shortcut. Will update later.
claunia added the Needs-TriageIssue-BugNeeds-Author-FeedbackNo-Recent-Activity labels 2026-01-31 06:56:10 +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 Issue-Bug Needs-Author-Feedback Needs-Triage No-Recent-Activity
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#19878
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?