musescore / musescore/MuseScore

Ctrl + F doesn't shift focus for pXX

Open
#33,932 3 comments 0 reactions 1 assignee View on GitHub

@shoogle is already working on this.

Since Jun 26, 2026.

accessibility needs review regression MS4
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 4.7 the Ctrl+F command doesn't seem to work if you type a page number such as p3. As general users haven't reported this I'm guessing it might be a screen reader navigation post the jump that isn't working anymore?

STEPS:

  1. Open a score with at least 4 pages.
  2. Press Ctrl+F
  3. Type p3 into the edit box and press enter. The screen reader announces "Page"
  4. Press left or right arrow and find you can't move.
  5. Repeat Steps 1-3 and this time try to move after the jump with Alt+Left or Alt + Right arrows. Notice that you will find yourself either in the title header area or on the final bar line which is typical of when MuseScore looses selection focus.
Supporting files, videos and screenshots

N/A

In which versions of MuseScore Studio is this issue present?

4.7.3

Regression

Yes, this used to work in a previous version of MuseScore 4.x

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.