[Bug]: Desktop: Series settings fields run under the scrollbar

Open Beginner friendly
#128 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
desktop

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

bug

[!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

  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.

More from tinystream-dev/tinystream

All issues in tinystream-dev/tinystream

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.