[Bug]: Desktop: Wanted rows wrap one word per line at narrow widths

Open Beginner friendly
#131 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
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
desktop

Research direction

The Wanted column layout is in desktop/app/src/browsing/view/wanted.rs around line 7. Start by running the reproduction from desktop/: cargo run --locked -- --scene wanted --size 820x640 --snapshot /tmp/w.png, then compare how the title and air-date columns are sized. Done means the title column fills and truncates while the date keeps a fixed or shrinking width with spacing at 820 px.

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?

On Wanted (desktop/app/src/browsing/view/wanted.rs:7) at 820 px wide, the episode title column gets squeezed to one word per line ("The / other / side") while the air-date column keeps its full width, with no gap between them.

Steps to reproduce

From desktop/, with a debug build: cargo run --locked -- --scene wanted --size 820x640 --snapshot /tmp/w.png

Expected behavior

The title keeps most of the width and truncates, and the date shrinks or moves under it.

Suggested fix

Make the title column Fill with truncation and give the date a fixed or shrinking width with 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.