musescore / musescore/MuseScore

Panels should scroll when focus is moved out of view via tab/arrow

Open
#25,571 1 comment 0 reactions 1 assignee View on GitHub

@shubham-shinde-442 is already working on this.

Since Nov 26, 2024.

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

Description

Update on 2024-12-16:

The following issue is no longer present in the Instrument and Mixer panels after #25664, but still occurs in the Properties panel (and possibly elsewhere).

Issue type

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

Description with steps to reproduce

Using arrows or tab in a scrollable panel will not scroll to the next focused thing.

Occurs in at least Properties, Instruments, and Mixer panels (not Palettes).

For example

  1. Create a score with many instruments and open the mixer
  2. Make your window small enough so the mixer and instruments panel both are scrollable.
  3. Tab to the first instrument in the Instruments panel, then arrow down to move focus down. See that at the bottom of the panel, focus moves beyond the bounds but the panel doesn't scroll to keep focus in view.
  4. Do the same for sounds in the mixer (using tab)
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/04afca92-b328-46d7-9d79-6cf278a3eaa7

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

Nightly

Regression

I was unable to check

Operating system

macOS 15.1

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.