Ctrl+Shift+W doesn't work if Ctrl key is remapped.

[kasajian]

Windows Terminal version (or Windows build number)

1.9.1942.0

Other Software

SharpKeys

Steps to reproduce

1. Install SharpKeys (or some other similar app) that maps the Caps+Lock key to the Ctrl key
2. open Windows Terminal, and create a tab or a pane.
3. Attempt to close the tab or pane with Ctrl+Shift+W
   (using the Caps+Lock key instead of the Ctrl iey)

Expected Behavior

pane or tab should close

Actual Behavior

It doesn't close. But if you use the actual Ctrl key, it will work.

Please note that this is not SharpKeys related. That product simply helps construct the data that needs to be placed in the registry. The key mapping is a Windows feature.

[DHowett]

@lhecker I suspect that this will be interesting to you!

[hsupu]

Same problem, Windows Terminal Version: 1.11.3471.0, remapping by SharpKeys (modify Registry)

I just failed to use Ctrl+Spacebar because remapped Ctrl to CapsLock. The original Ctrl works.

UPDATE: 1.12.10393.0 still not work

UPDATE: For laptop, remapped Ctrl works on external keyboard, neither original nor remapped Ctrl works on internal keyboard; for PC, it has only external keyboard so the remapped key works. I don't understand..

[manifestinteractive]

@kasajian thanks for posting, thought I was going crazy experiencing the same thing.

[jcrben]

I noticed that the remapped Caps Lock doesn't work right in this case on my work machine, but on my personal machine using PowerToys Keyboard Manager I'm not having the same issue.

Personal machine
Attaching the system info for my personal thinkpad t480 running Windows 10.
systeminfo.txt

Keyboard Manager right now is 0.70.1 0.74.1 - installed via winget - and my configuration is minimal:

Work machine
It's a Dell 5420 - not attaching more details. My work doesn't let me install PowerToys so I've tried AHK instead.

[kasajian]

How can we get this to be fixed?

The developers who wrote this clearly aren't handling the Ctrl key the right way. It's fine. Mistakes happen. But why not fix it after you're told about it?

It's been like 3 years.

How do we get this thing attention?

[zadjii-msft]

Anyone is welcome to investigate yourself what's up here. The code that handles keybindings is right here:

terminal/src/cascadia/TerminalControl/TermControl.cpp

Line 1749 in 3a06826

bool TermControl::_TryHandleKeyBinding(const WORD vkey, const WORD scanCode, ::Microsoft::Terminal::Core::ControlKeyStates modifiers) const

That's where I'd start with a breakpoint.

There's but a single 👍 on this issue, which means this probably isn't bubbling to the top of our list of priorities any time soon. But we'd be happy to review a fix