Plugin: sheet music can't be scrolled by hand before playback
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start with the sheet-music view’s .jingle styles and the src/views/HomeView.vue layout described in the issue. Check how the card’s height and overflow interact with OSMD’s followCursor while stopped and during playback. Done means a long score can be scrolled by hand while stopped, and playback keeps the cursor in view by scrolling the card.
Written by the indexing model from the issue text.
Description
In the sheet-music view, a score longer than the host's panel can't be scrolled by hand while the audio is rendering or stopped.
Why (from the code; not reproduced in a browser)
- MulmoChat puts the View in a
flex-1 min-h-0 overflow-hiddenbox (src/views/HomeView.vue), so the host does not scroll it. - The View's root
.jinglehas no height and nooverflow-y, so nothing in the card scrolls either. - During playback it seems to scroll because OSMD's
followCursorcallsscrollIntoView, which scrolls even anoverflow: hiddenancestor programmatically. Before playback the cursor doesn't move, so the bottom of the score can't be reached.
Fix
Give .jingle height: 100% and overflow-y: auto, so the card scrolls itself. While playing, following the cursor as now is fine (the user doesn't need to scroll by hand then); check that followCursor then scrolls the card and still keeps the cursor in view.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 0
- Avg merge
- 2h 17m
- Merged PRs (30d)
- 39
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 receptron/jinglescript
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
receptron/jinglescript#48 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 78/100
receptron/jinglescript#43 ·
Maintainers usually reply within 1 day
All issues in receptron/jinglescript
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
components-web-app/docs#307 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
localstack/localstack-mcp-server#112 ·
Maintainers usually reply within 1 day
-
area:frontend kind:bug priority:p1 ready
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
PhyberApex/kuroshiro#1687 ·
Maintainers usually reply within 1 day
-
Performance (Web Vitals) collector: LCP/FCP from background tabs are not discarded, inflating p75Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
umami-software/umami#4720 ·
Maintainers usually reply within 3 days