Skip to content

palette: ⌘K leaves a press the page already answered - #23

Open
Darkhorse7stars wants to merge 1 commit into
mainfrom
fix/palette-claimed-chord
Open

Darkhorse7stars wants to merge 1 commit into
mainfrom
fix/palette-claimed-chord

Conversation

@Darkhorse7stars

Copy link
Copy Markdown
Member

On hanzo.ai/dev, Ctrl+K in New run's text box opens the composer's own Commands list (Run, … Use a git URL), and the composer claims the press with preventDefault. summons (pkg/app/src/seek.ts) opened the palette on top of it anyway, from both window listeners (App, Shell). So one press opened two lists, and what was typed next went to Search or jump to…, whose last row is Log out. A click aimed at the composer's commands signed the person out.

  • seek.ts: summons reads defaultPrevented, so a press something on the page already answered isn't the palette's. A field that answers nothing still opens it, as before.
  • chord.ts: Press carries defaultPrevented?.
  • seek.test.ts: a claimed press doesn't summon, from a field or anywhere else.

hanzo.ai pins @hanzo/app 0.2.63, so it'll carry the same change in its existing 0.2.63 patch until the pin moves.

Dev's composer (@hanzo/ui) opens its own commands on Ctrl+K and claims
the press with preventDefault. summons opened the palette over them
anyway, from App's and Shell's window listeners, so one press opened two
lists: what was typed next went to "Search or jump to…", whose last row
is Log out, and a click meant for the composer's commands signed the
person out.

summons now reads defaultPrevented: a press something on the page
answered is not the palette's. A field that answers nothing still opens
it, as before.
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