logseq / logseq/db-test

`/` Command popup persists when entering edit mode on another block

Closed
#1,188 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Search first
  • I searched and no similar issues were found
What Happened?

The / command popup does not disappear as expected.

After opening the / command popup in a block, if an item is not selected and the user enters edit mode on a different bullet, the / command popup remains visible and is displayed in the newly selected bullet.

Reproduce the Bug
  1. Place the cursor in a block.
  2. Type / to open the / command popup.
  3. Do not select any command from the popup.
  4. Select a different bullet and enter edit mode.
  5. Observe that the / command popup is still displayed in the newly selected bullet.
Expected Behavior

The / command popup should disappear when the user leaves the original block without selecting a command.

Screenshots

No response

Files

No response

Browser, Desktop or Mobile Platform Information

windows 11
logseq 2.0.1-alpha+nightly.20260907

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.
  • I'm willing to submit a PR (Thank you!)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by opening the / command popup, leaving the original block, and entering edit mode on another bullet. Trace the popup's lifecycle across the block-change and edit-mode transition; done means the popup disappears when leaving the original block without selecting a command.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.