Draw a tune's notes at a size that reads easily, wrapping its bars and using the margin beside it
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by finding the music fence renderer and how it configures abcjs in Work, Edit, and Present. Check how the available width and adjacent margin are determined, then compare abcjs's wrap and staff width options. Done means notes stay readable, bars wrap in narrow columns, and Work can use the otherwise empty margin beside the staff.
Written by the indexing model from the issue text.
Description
A music fence draws its staff exactly as wide as the text and fits the whole line of bars into it, so in a narrow column the notes are small.
In Work, on a window 1280 pixels wide, the staff is 503 pixels, the margin beside it 312 pixels and empty when no aside is there, and a note's head is about 20 pixels; in Edit's column, beside the editor, it's smaller still. In Present the notes are easy to see.
```music
X:1
T:Twinkle, Twinkle
M:4/4
L:1/4
K:C
C C G G | A A G2 | F F E E | D D C2 |]
```
Today: however narrow the column, the four bars are fitted onto one line, and the notes shrink to fit.
Instead:
- Notes are drawn at a size that reads easily, and a tune wraps onto more lines when its column is too narrow for them, as abcjs can (
wrap, with a set staff width). It's bigger in Edit and on a phone too, at the cost of a taller tune. - In Work, a staff takes the margin beside it too, when no aside is next to it, as the margin is otherwise empty.
Widening Work's text column for everything was turned down: every paragraph's lines would grow past what reads easily.
Came up in the retro of the 2026-11-16 review, from #99.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 26
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from jzheaux/reader
-
polish
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
accessibility bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
polish
Difficulty 3/5 1-2 days Newbie friendliness 64/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OWASP/CheatSheetSeries#3018 ·
Maintainers usually reply within 1 day
-
Radix number block generates NaN after switching a negative or decimal number to binary, octal or hexPossibly taken @matthewalberto claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
mit-cml/appinventor-sources#4246 · 1 comment ·
Maintainers usually reply within 1 day
-
marketing
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
GoogleChrome/modern-web-guidance-src#3675 · 2 comments ·
Maintainers usually reply within 1 day