Command palette navigation annoyance #15681

Closed
opened 2026-01-31 04:45:24 +00:00 by claunia · 2 comments
Owner

Originally created by @elsaco on GitHub (Oct 24, 2021).

Windows Terminal version (or Windows build number)

Windows Terminal Preview ver. 1.12.2931.0

Other Software

No response

Steps to reproduce

  1. open command palette
  2. using keyboard navigate to a sub-command palette, currently there are three options:
New Tab...
Select color scheme...
Split pane...
  1. try to navigate back using keyboard

Expected Behavior

  1. navigate command palette using keyboard only

Actual Behavior

  1. mouse click required to get back to previous command palette:

wt_cmd_palette_back

Originally created by @elsaco on GitHub (Oct 24, 2021). ### Windows Terminal version (or Windows build number) Windows Terminal Preview ver. 1.12.2931.0 ### Other Software _No response_ ### Steps to reproduce 1. open command palette 2. using keyboard navigate to a sub-command palette, currently there are three options: ``` New Tab... Select color scheme... Split pane... ``` 3. try to navigate back using keyboard ### Expected Behavior 1. navigate command palette using keyboard only ### Actual Behavior 1. mouse click required to get back to previous command palette: ![wt_cmd_palette_back](https://user-images.githubusercontent.com/3933920/138615973-e21f0947-0dce-4607-8df4-c0417e965ab2.png)
Author
Owner

@zadjii-msft commented on GitHub (Oct 25, 2021):

FWIW you can hit tab to move focus to the back button, then hit space to go back. Also, deleting the > and typing it back will take you back to the root. What key would you suggest to go back?

@zadjii-msft commented on GitHub (Oct 25, 2021): FWIW you can hit <kbd>tab</kbd> to move focus to the back button, then hit space to go back. Also, deleting the `>` and typing it back will take you back to the root. What key would you suggest to go back?
Author
Owner

@ghost commented on GitHub (Nov 3, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Nov 3, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15681