F16 Is not usable in Terminal

[richardcox13]

Windows Terminal version

1.16.10261.0

Windows build number

10.0.19044.2604

Other Software

Happens running cmd or pwsh 7.3.2 within the tab.

Steps to reproduce

Have a keyboard with additional function keys.
Run an app that reports key presses.
In terminal F13, F14, & F15 work. But F16 does not: no input is seen. Also cannot map to a WT action.

The test application works with F16 (including with modifiers) under conhost.exe. Also seen (and mappable) in Visual Studio 2022 (didn't check earlier versions).

Expected Behavior

See keyboard input when F16 is pressed. Can map to actions, and when pressed that action is triggered.

Actual Behavior

F16 does nothing in Windows Terminal and applications running within Windows Terminal.

[zadjii-msft]

Curious. We do have a (de)serializer for f16

    XX(VK_F16, L"f16")                                   \

It's not in any of the terminalInput.cpp maps, but that's only relevant for VT input. If it works for conhost, then you're most likely not even hitting the VT input path.

Can you try repro'ing this with the debug tap to get a trace of all the input and output/? Once the bug starts occurring, send us a screenshot and we might be able to figure out what the Terminal thinks it's getting here.

[richardcox13]

Before any interaction:

then just switch focus to Windows Terminal and press F16:

Hope this is understandable....

[richardcox13]

Should note there certainly was extra additional red text appearing when I hit F16.

[zadjii-msft]

␛[123;88;0;1;32;1_

• ␛[123;88;0;1;32;1_
  • Vk: VK_F12
  • Sc: 88
  • Uc: 0
  • Kd: down
  • Cs: 32

huh

[zadjii-msft]

Yea that's super weird. Looks like the key the Terminal thinks it's getting is F12, not F16. 123 is 0x7b which is VK_F12. VK_F16 would be 0x7f.

I honestly don't know where to investigate that next. If you can build the Terminal from source, I might be able to point you at a function to see what we're getting there.

I might be able to reconfigure my keyboard to have a F16 key. The issue I'd worry about there is that this was more specific to your keyboard/layout, and my keyboard firmware wouldn't repro it 😕 Just out of curiosity, what keyboard & layout are you using?

[richardcox13]

The keyboard is a Keychron K6 (UK/ISO) with no customisations.

Outside of Windows Terminal it is seen as F16 ('NET's Console.ReadKey and in Visual Studio's keyboard customisation).

I can have a go at debugging: any hints on getting a development environment running (it has been a long time since I did any Win32/C/C++ development).