Skip to content

fix(dashboard): responsive summary panels - #4

Merged
Kadreev merged 1 commit into
mainfrom
fix/dashboard-responsive-panels
Oct 7, 2026
Merged

Kadreev merged 1 commit into
mainfrom
fix/dashboard-responsive-panels

Conversation

@Kadreev

@Kadreev Kadreev commented Oct 7, 2026

Copy link
Copy Markdown
Owner

What

The dashboard's summary panels broke at common widths:

  • Issues by feature overflowed its panel. The list's grid track sized to the longest one-line feature name, so on a 1310 px window the list ran ~70 px under the severity panel.
  • A long feature list stretched every panel in the row. With 34 features, all three panels were ~1,450 px tall and severity and the work queue were mostly empty.

Changes

  • Panels are one column on a phone. From 720 px, issues by feature spans the row above severity and the work queue. From 1100 px it gets a wider column (1.6fr). Every track is minmax(0, …), so content can't push past its panel.
  • Feature rows truncate long names with an ellipsis (full name on hover) instead of widening the list.
  • The top 8 features stay visible, and the rest fold into a <details> with a "Show all N features" / "Show fewer" toggle. No script, keyboard-accessible, hidden in print.
  • The severity table scrolls inside its panel on narrow screens.

Verified

  • node --test: 183 pass, including 2 new render tests (top-8 fold, overflow-safe CSS), both written failing first. The demo tracker validates.
  • Browser check against a real 34-feature tracker at 1440, 1024 and 375 px: no panel or page overflow, and panels are 414 px tall at desktop width.

🤖 Generated with Claude Code

Issues by feature overflowed its panel: the list's grid track sized to the
longest nowrap feature name, so on a 1310px window it ran 70px under the
severity panel. And its 34-row list stretched every panel in the row to
~1,450px, leaving severity and the work queue mostly empty.

- Panels: one column on a phone; from 720px issues by feature spans the
  row over severity and the work queue; from 1100px it gets a 1.6fr
  column. Every track is minmax(0, …), so nothing pushes past its panel.
- Feature rows use minmax(0, 1fr): long names truncate (full name on
  hover) instead of widening the list.
- The top 8 features stay visible; the rest fold into a <details> with a
  "Show all N features" / "Show fewer" toggle, no script.
- The severity table scrolls inside its panel on a narrow screen.

Checked at 1440, 1024 and 375px against a 34-feature tracker: no panel or
page overflow; panels 414px tall at desktop width.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-07T00:45:18.740022Z 39f1d79 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 39f1d79957

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/dashboard-summary.mjs
@media print {
.summary { margin-top: 8px; }
.card, .panel { break-inside: avoid; box-shadow: none; }
.feat-more > summary { display: none; }

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Expand folded feature rows when printing

When the dashboard has more than eight features with open issues and the user selects Export PDF without opening the disclosure, src/server.mjs calls window.print() while the <details> remains closed. This rule hides the toggle but does not override the browser's hiding of a closed <details> element's other children, so the PDF silently omits every feature after the first eight. The print styles should explicitly display the nested .feat-rows, or the export handler should temporarily open the disclosure.

Useful? React with 👍 / 👎.

@Kadreev
Kadreev merged commit d3e0c3d into main Oct 7, 2026
6 checks passed
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