Confusing behavior in Command Palette when pressing "Home" during search #11312

Closed
opened 2026-01-31 02:44:07 +00:00 by claunia · 3 comments
Owner

Originally created by @Don-Vito on GitHub (Nov 7, 2020).

Environment

Development branch

Steps to reproduce

  1. Open command palette.
  2. Input some search text
  3. Scroll Down a bit
  4. Now press home
  5. Press home again

ConfusingHome

Expected behavior

Home should be disabled either in search box or in the command palette.
Same of course applies to End.

Actual behavior

  1. The first occurrence of Home goes to the beginning of the filter
  2. The second occurrence of Home scrolls the palette
Originally created by @Don-Vito on GitHub (Nov 7, 2020). # Environment Development branch # Steps to reproduce 1. Open command palette. 2. Input some search text 3. Scroll Down a bit 4. Now press home 5. Press home again ![ConfusingHome](https://user-images.githubusercontent.com/4639110/98452152-6c6dbd00-2155-11eb-874b-e127a9cce63e.gif) # Expected behavior Home should be disabled either in search box or in the command palette. Same of course applies to End. # Actual behavior 1. The first occurrence of Home goes to the beginning of the filter 2. The second occurrence of Home scrolls the palette
Author
Owner

@Don-Vito commented on GitHub (Nov 8, 2020):

@Hegunumo - I also opened this. Please let me know how you see it.

@Don-Vito commented on GitHub (Nov 8, 2020): @Hegunumo - I also opened this. Please let me know how you see it.
Author
Owner

@KevinCathcart commented on GitHub (Nov 11, 2020):

For what is it worth, it looks (from experimentation) like VSCode does the following:

Horizontal navigation commands like or Home affect the text box. Vertical navigation commands like ,PgUp, or Ctrl+Home affect the list.

That seems to me to be a logical way to differentiate without losing functionality. Of course, how to actually implement that cleanly may still be an open question.

@KevinCathcart commented on GitHub (Nov 11, 2020): For what is it worth, it looks (from experimentation) like VSCode does the following: Horizontal navigation commands like <kbd>←</kbd> or <kbd>Home</kbd> affect the text box. Vertical navigation commands like <kbd>↓</kbd>,<kbd>PgUp</kbd>, or <kbd>Ctrl</kbd>+<kbd>Home</kbd> affect the list. That seems to me to be a logical way to differentiate without losing functionality. Of course, how to actually implement that cleanly may still be an open question.
Author
Owner

@ghost commented on GitHub (Jan 28, 2021):

:tada:This issue was addressed in #8194, which has now been successfully released as Windows Terminal Preview v1.6.10272.0.🎉

Handy links:

@ghost commented on GitHub (Jan 28, 2021): :tada:This issue was addressed in #8194, which has now been successfully released as `Windows Terminal Preview v1.6.10272.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.6.10272.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11312