microsoft/Terminal

F16 Is not usable in Terminal

Open

#14,907 opened on Feb 25, 2023

View on GitHub
 (7 comments) (0 reactions) (0 assignees)C++ (3,212 forks)batch import
Area-InputArea-TerminalControlHelp WantedIssue-BugPriority-3Product-Terminal

Repository metrics

Stars
 (35,764 stars)
PR merge metrics
 (Avg merge 27d 19h) (24 merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Look for the key code mapping table in the source code and add the F16 key with its virtual key code (VK F16). Verify the expected behavior by running the existing tests.
Tech stack
None
Domain
clibackend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75