[Bug]: Desktop: Calendar episode cards break at narrow widths

Open
#130 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
63/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust

Research direction

Start at desktop/app/src/browsing/view/calendar.rs:41, where the week grid is fixed to seven columns, and reproduce with cargo run --locked -- --scene calendar --size 820x640 --snapshot /tmp/c.png from desktop/. Trace how column width is computed and where the thumbnail, time badge and countdown are laid out, then add a minimum column width and a narrow-width fallback. Done when the snapshot at 820x640 renders a readable week with no spilled badge or clipped countdown.

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?

The calendar always shows seven columns (desktop/app/src/browsing/view/calendar.rs:41). At 820 px wide, each column is about 60 px: the episode thumbnail shrinks to a pill, its time badge spills outside it, and "in 59:59" is cut to "in 59:5".

Steps to reproduce

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

Expected behavior

The week stays readable at narrow window sizes.

Suggested fix

Give columns a minimum width and switch to fewer columns or a day list below it (as narrow web layouts do), and let the badge and countdown truncate gracefully.

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.