Make sure that key bindings work in all IMEs

[yola-0316]

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]  
Platform ServicePack Version      VersionString 
-------- ----------- -------      ------------ 
Win32NT             10.0.19041.0 Microsoft Windows NT 10.0.19041.0

Windows Terminal version (if applicable):
1.0.1401.0

Any other software?

Steps to reproduce

ctrl+, open settings.json, find keybindings tutorial in microsoft docs
modify some keybindings like that:

{ "command": "openNewTabDropdown", "keys": "ctrl+shift+d" },        // will work
{ "command": "openNewTabDropdown", "keys": "ctrl+shift+space" }, // not work

 { "command": { "action": "newTab", "index": 0 }, "keys": "ctrl+1" },     // will work
 { "command": { "action": "newTab", "index": 1 }, "keys": "ctrl+2" },     // will work
 { "command": { "action": "newTab", "index": 2 }, "keys": "ctrl+shift+3" },     // not work
 { "command": { "action": "newTab", "index": 3 }, "keys": "ctrl+shift+4" },     // not work

Expected behavior

keybindings work properly

Actual behavior

some keybindings not work

settings.json

GitHub not support upload .json file, modify the extension to .txt
settings.txt

[DHowett]

This is strange!
What keyboard layout are you using?

[yola-0316]

---

Resolved!
Conflicted with other shortcuts.
ctrl+shift+space conflict with IME shortcut ctrl+space Chinese/English mode toggle.
ctrl+shift+NUMBER, when I quit the most app, it worked, I need to find which app affected.
Wish to have some notify when keybindings have used by another application.

---

@DHowett I use US keyboard layout.
Just now, I discovered the effect of input methods on keybindings.
When I switch IME to English US. One of the keybindings worked.

{ "command": "openNewTabDropdown", "keys": "ctrl+shift+d" },        // will work
{ "command": "openNewTabDropdown", "keys": "ctrl+shift+space" }, // will work under English US

but this still not work

 { "command": { "action": "newTab", "index": 2 }, "keys": "ctrl+shift+3" },     // not work  
 { "command": { "action": "newTab", "index": 3 }, "keys": "ctrl+shift+4" },     // not work

Before, I used the English status of Chinese input

It may be that the input method has affected keybinds?

[DHowett]

I will reopen this issue, because we want to make sure that key bindings work in all IMEs :)

[lhecker]

Just now, I discovered the effect of input methods on keybindings.
When I switch IME to English US. One of the keybindings worked.

I think that part should work now with the introduction of #10876, which was released in Windows Terminal 1.11.

[zadjii-msft]

(also cross-linking: #15598. ctrl+shift+f for find doesn't work with the Microsoft Pinyin IME)

[zadjii-msft]

We discussed this a little while back, and we've come to the conclusion as a team that it's going to be practically impossible for us to avoid conflicts with all keys bound in all possible software that someone might be using with the Terminal. We will try our best to stick to ctrl+shift modifiers for keys we bind in our default settings, to avoid conflicts with CLI apps. And we'll always let users change bindings for keys on their own. But there's not much else we can do here to try and avoid the gambit of other things that might also bind keys.