microsoft/Terminal

Keyboard focus improvements for font features/axes

Open

#19713 opened on Jan 6, 2026

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C++ (35,764 stars) (3,212 forks)batch import
Area-UserInterfaceHelp WantedNeeds-Tag-FixProduct-Terminal

Description

Adding an item is generally done by clicking the "add new" button and selecting an item from the flyout. However, when you do this from the keyboard, it feels a little weird. Your focus stays on the add new button.

Ideally, it would move to the newly added item.

This is particularly bad if the user added the last feature/axes. Since that disables the add new button, the button can't be focused, so it gets yeeted to the tab row.

Contributor guide

Tech stack
cpp
Domain
accessibility
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C++ knowledgeXAML focus management
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Examine the focus management in the font features/axes UI, likely in files under src/cascadia/TerminalSettingsEditor. Look for the 'add new' button's event handler and ensure that after adding an item, focus moves to the newly added element. Consider the edge case when the last item is added and the button becomes disabled.