musescore / musescore/MuseScore

Inconsistent Vertical Scrolling (Smooth in Palette, Stepwise in Score Body)

Open
#24,089 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

blocked externally UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce
  1. Create new score
  2. Expand several items in the palette so that a scrollbar appears
  3. Scroll with a mouse wheel in the palette
  4. Scroll with a mouse wheel in the score body
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/918a6f02-feb6-44f5-9224-c84b7b533062

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

4.3.2-241630832, revision: github-musescore-musescore-22b46f2

Regression

No.

Operating system

macOS 14.6, Arch.: x86_64

Additional context

I've included Chrome and a directory to show that step-wise scrolling is the expected behavior. I'm someone who strongly dislikes smooth scrolling, and have it disabled in applications that implement their own scrolling behavior outside of the operating system. The palette both scrolls smoothly and seems to be at a slightly different speed, behaving different from everything else on my computer, so the bug in my mind is how the palette has implemented vertical scrolling.

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.

Research direction

Reproduce the issue in a new score by expanding palette items, then compare mouse-wheel scrolling in the palette and score body on macOS or Arch Linux. No source files or tests are named; trace the two scrolling paths and consider the issue done when both use the expected stepwise behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.