[Bug]: Desktop: Series settings fields run under the scrollbar
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Start at desktop/app/src/browsing/view/overlays.rs:676, where the series settings scroll area and its text fields (Preferred groups, Also known as, File names) are laid out; check how the scroll area's content width is computed relative to the scrollbar. Reproduce with cargo run --locked -- --scene series-settings --snapshot /tmp/s.png from desktop/, and compare against other dialogs that already inset their content. Done looks like the fields ending before the scrollbar with their full border and rounded corners visible in the snapshot.
Written by the indexing model from the issue text.
Description
[!NOTE]
This issue was written by Claude (Claude Opus 5.5) from a review session of the desktop app (#80) with @PhrolovaMoe. It was found in headless renders of the debug build's fixture scenes (--snapshot), not on a live server.
Version
0.40.0 (feat/desktop, 017a837b)
Area
Other (desktop app)
What happened?
In the series settings dialog (desktop/app/src/browsing/view/overlays.rs:676), the text fields (Preferred groups, Also known as, File names) fill the full width of the scrollable area, so the scrollbar covers their right edges and their rounded corners and border are cut off.
Steps to reproduce
From desktop/, with a debug build: cargo run --locked -- --scene series-settings --snapshot /tmp/s.png
Expected behavior
Fields end before the scrollbar, with their full border visible.
Suggested fix
Give the scrollable content right padding equal to the scrollbar width (or use an overlay scrollbar spacing).
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 1
- Avg merge
- 4h 49m
- Merged PRs (30d)
- 5
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No 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 tinystream-dev/tinystream
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tinystream-dev/tinystream#132 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tinystream-dev/tinystream#131 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
tinystream-dev/tinystream#129 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tinystream-dev/tinystream#124 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tinystream-dev/tinystream#123 ·
All issues in tinystream-dev/tinystream
Similar issues
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
sandbox-quantum/switch#2163 ·
Maintainers usually reply within 1 day
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area/dashboard kind/bug QA/dev-automation
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pydantic/pydantic-ai#13939 ·
Maintainers usually reply within 1 day
-
self-host
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
funmusicplace/mirlo#2625 ·
Maintainers usually reply within 1 day