Skip to content

fix(web): Keep the results list readable below 1024px - #30

Merged
OffCrazyFreak merged 1 commit into
mainfrom
fix/web-responsive
Sep 16, 2026
Merged

OffCrazyFreak merged 1 commit into
mainfrom
fix/web-responsive

Conversation

@OffCrazyFreak

@OffCrazyFreak OffCrazyFreak commented Sep 16, 2026 •

Copy link
Copy Markdown
Owner

Changes:

  • Show the sources and gains columns from the lg breakpoint instead of md, so tablets get the stacked row
  • Let the row title, author line and phone gains line wrap to two lines instead of truncating
  • Stack the summary headline over the select presets until lg
  • Hide the "How it decides" link in the header under 640px and stop the nav from wrapping

Measured with a headless sweep at 360, 390, 768, 1024 and 1440 px, through the sample run, the detail dialog, the write confirmation and the loading and failure screens. Before: the five column grid started at 768 px and left the title column 98 px wide, narrower than on a phone, so every title in the sample was cut; on phones the title column was 114 px and truncated most titles, and "How it decides" wrapped into the wordmark in the sticky header. After: no row text is clipped at 768 px, titles wrap on phones, and the header shows the name and GitHub without overlap. At 1024 px and wider the columns are unchanged; a title or author line longer than its cell now wraps to a second line there too instead of being cut, which the sample titles are too short to show.

Checks: pnpm typecheck, pnpm format:check, pnpm test (42 passed), pnpm build, node scripts/pyodide-smoke.mjs (333 passed under Pyodide).

Changes:
- Show the sources and gains columns from the lg breakpoint instead of md, so tablets get the stacked row
- Let the row title, author line and phone gains line wrap to two lines instead of truncating
- Stack the summary headline over the select presets until lg
- Hide the "How it decides" link in the header under 640px and stop the nav from wrapping

Measured with a headless sweep at 360, 390, 768, 1024 and 1440 px: the five column grid started at 768 px and left the title column 98 px wide, narrower than on a phone, so every title in the sample was cut. On phones the title column was 114 px and truncated most titles, and "How it decides" wrapped into the wordmark in the sticky header. After the change no row text is clipped at 768 px, titles wrap on phones, and the header shows the name and GitHub without overlap.

Notes:
- Nothing changes at 1024 px and wider
@coderabbitai

coderabbitai Bot commented Sep 16, 2026 •

Copy link
Copy Markdown

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: bdd5fb82-bc5a-41f6-a496-9087815ca4b1

📥 Commits

Reviewing files that changed from the base of the PR and between cd4f7ed and db12216.

📒 Files selected for processing (1)
  • web/src/App.tsx

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


Summary by CodeRabbit

  • Style
    • Updated responsive layouts so header navigation, summaries, results, and gains columns adapt at larger screen widths.
    • Hid the “How it decides” link and gains columns on smaller screens.
    • Allowed row titles and author information to display up to two lines for improved readability.

Walkthrough

The web interface now uses desktop breakpoints for header, summary, and results layouts. Result titles, author lines, and compact gains can display up to two lines.

Changes

Responsive layout updates

Layer / File(s) Summary
Header and summary breakpoints
web/src/App.tsx
Header navigation and the Summary grid now switch layouts at the lg breakpoint. The “How it decides” link appears at lg and wider.
Results columns and row content
web/src/App.tsx
Results columns and row controls now use the lg breakpoint. Titles, author lines, and compact gains use two-line clamping.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to db122

The responsive layout changes are mergeable; the investigated tablet link regression is not present.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 1 files. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly and concisely describes the main responsive layout change for the web results list below 1024px.
Description check ✅ Passed The description directly explains the responsive breakpoint changes, text wrapping behavior, header updates, validation coverage, and test results.
  • Fix all pre-merge checks with AI
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
  • Create stacked PR
  • Commit on current branch

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

A rabbit hops where breakpoints grow
The wider paths now neatly show
Two lines hold each title bright
Gains appear at desktop height
Header links wait for room
And tidy grids make space to bloom

Comment @coderabbitai help to get the list of available commands.

@OffCrazyFreak
OffCrazyFreak merged commit cc46dd7 into main Sep 16, 2026
4 checks passed
@OffCrazyFreak
OffCrazyFreak deleted the fix/web-responsive branch September 16, 2026 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant