musescore / musescore/MuseScore

Keyboard Navigation not working correctly in Note Input Mode

Open
#28,532 0 comments 0 reactions 1 assignee View on GitHub

@shoogle is already working on this.

Since Jun 24, 2025.

accessibility needs review
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Accessibility issue (e.g. for keyboard-only or screen reader users)

Description with steps to reproduce

In Note Input Mode Ctrl F doesn’t work, Ctrl Home doesn’t work if you arrow after it, alt arrow does. It has been suggested this is likely because Ctrl Home selects the first bar line so in note input mode which only selects notes & rests it gets stuck.

STEPS:

  1. Move a few bars into a score and press N for note input mode.
  2. Press Ctrl F, type in a bar number and press enter.
  3. Actual Behaviour: Nothing happens, focus is unchanged.
  4. Expected Behaviour: Focus moves to the bar that was typed.
  5. Press Ctrl Home. You hear “bar line single bar line bar 1 beat 1”.
  6. Press right arrow.
  7. Expected behaviour: Focus moves to the next note/rest in bar 1.
  8. Actual Behaviour: Focus moves to the next note/rest from where you were before you pressed Ctrl Home.
Supporting files, videos and screenshots

N/A

What is the latest version of MuseScore Studio where this issue is present?

4.5.2

Regression

I was unable to check

Operating system

Windows 11 with NVDA

Additional context

No response

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

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.