musescore / musescore/MuseScore
Changing header Y-offset doesn't work symmetrically to footer Y-offset
@davidstephengrant is already working on this.
Since Sep 8, 2026.
- 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
Let's start with footer at default position.
Change the Y-offset of the footer in Style:
-
if you increase it, the footer will just go outside the page, (correctly) moving indipendently from the rest of the score
-
if you decrease it, the footer will (correctly, again) "push up" the lower staff in order to avoid collision:
Now, let's try with the header, with its default position and "mirroring" the actions we did with the footer:
-
if you increase the Y-offset, the header will just trespass the first staff, without avoiding any collision:
-
if you decrease the Y-offset, the header will move outside the page (as expected), but it will "push down" the first staff as it would be expected for case 1.
Supporting files, videos and screenshots
Footer correct behaviour:
https://github.com/user-attachments/assets/f6e7c85b-3274-444c-8934-3cc353661c8d
Header incorrect behaviour:
https://github.com/user-attachments/assets/5cab3be7-7e79-4db4-ba88-19a6e25f063b
In which versions of MuseScore Studio is this issue present?
4.0.2–4.7.5
Regression
No
Operating system
Windows 11
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.