logseq / logseq/db-test

Keyboard navigation does not scroll the `/` command popup

Open
#1,186 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

- [x] I searched and no similar issues were found

### What Happened?

When using the `/` command popup, navigating through the items with the **Up/Down arrow keys** does not scroll the popup.

As a result, keyboard navigation does not work properly when navigating through items beyond the currently visible area.

### Reproduce the Bug

1. Create or edit a block.
2. Type `/` to open the command popup.
3. Use the **Up/Down arrow keys** to navigate through the commands.
4. Continue navigating until the selected item moves beyond the currently visible area.

### Expected Behavior

The popup should automatically scroll to keep the currently focused item visible when navigating with the Up/Down arrow keys.

### 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 in a block editor by opening the `/` command popup and navigating with the Up/Down arrow keys. Trace the popup's keyboard-navigation entry point and verify that the focused command remains visible while moving beyond the current viewport.

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
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.