[Bug]: Desktop: Calendar episode cards break at narrow widths
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
- Domain
- desktop-dev, frontend
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
[!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
- 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 76/100
tinystream-dev/tinystream#128 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tinystream-dev/tinystream#124 ·
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