coderaiser / coderaiser/cloudcmd

Insert key behavior: selection should automatically move cursor to the next item

Open
#471 3 comments 0 reactions 1 assignee View on GitHub

@coderaiser is already working on this.

Since Aug 18, 2026.

bug
Dominant language
JavaScript
Stars
2k
Forks
270
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
In classic orthodox file managers, pressing the Insert key toggles the selection of the current file and automatically moves the cursor down to the next file. In Cloud Commander, the Insert key toggles the selection, but the cursor remains on the same item, which requires alternating between Insert and the Down arrow to select multiple consecutive files.

To Reproduce / Steps to reproduce the behavior:

  1. Open Cloud Commander in your browser.
  2. Navigate to any folder containing multiple files.
  3. Focus on a file and press the Insert key.
  4. See that the file is selected, but the cursor does not move to the next row.

Expected behavior
Pressing the Insert key should toggle the selection state of the current item AND automatically advance the cursor down to the next item in the list. This allows users to rapidly select consecutive files by simply pressing the Insert key repeatedly.

Screenshots
Not applicable.

Desktop (please complete the following information):

Version (cloudcmd -v): latest (Docker image)
Node Version node -v: (Inside Docker image)
OS (uname -a on Linux): Linux (Docker host)
Browser name/version: Chrome / Firefox / Edge (Any modern browser)
Used Command Line Parameters: Docker default

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.