Skip to content

fix(web): open the command palette with Ctrl/Cmd+Shift+K - #971

Closed
thedancingdeveloper wants to merge 1 commit into
mainfrom
fix/firefox-ctrl-k-palette
Closed

thedancingdeveloper wants to merge 1 commit into
mainfrom
fix/firefox-ctrl-k-palette

Conversation

@thedancingdeveloper

Copy link
Copy Markdown
Contributor

Summary

  • Ctrl/Cmd+K never opened the command palette in Firefox. Firefox reserves bare Ctrl+K ("Search the web") in its own shortcut layer and does not deliver the keydown to the page, so the existing preventDefault on the window listener never ran.
  • The palette chord is now Ctrl/Cmd+Shift+K. That combination is not reserved by Firefox or by Chrome's omnibox Ctrl+K, and xterm only claims unmodified Ctrl+letter, so a focused terminal still lets it through.
  • Button titles (Go to…), the shortcut help registry, and the user-guide keyboard table all name the new chord. The registry test asserts Shift+Ctrl+K matches and bare Ctrl+K does not.

Test plan

  • pnpm test in web/ — 138 files, 1149 tests passed
  • In Firefox, Ctrl+Shift+K opens the palette from a non-terminal surface and from a focused terminal; Ctrl+K still does the browser's own search

Firefox claims bare Ctrl+K ("Search the web") in its own shortcut layer
and never delivers the keydown to the page, so preventDefault on the
app listener cannot win it. Ctrl/Cmd+Shift+K is not reserved by Firefox
or by Chrome's omnibox, and xterm only claims unmodified Ctrl+letter, so
a focused terminal still lets the chord through.
@thedancingdeveloper

Copy link
Copy Markdown
Contributor Author

Closing to fold into the single integration PR (integrate/vogt-next) per operator: one large PR to reduce CI runs. Branch kept; review continues on the branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant