Skip to content

Align expanded background-command icons with the header icon#275

Merged
SawyerHood merged 1 commit into
mainfrom
fix/background-commands-icon-align
Jun 19, 2026
Merged

Align expanded background-command icons with the header icon#275
SawyerHood merged 1 commit into
mainfrom
fix/background-commands-icon-align

Conversation

@SawyerHood

Copy link
Copy Markdown
Collaborator

Summary

In the expanded background-commands card, the child-row terminal icons didn't line up under the header row's icon. The header icon sits inside the toggle <button>, which adds its own px-1 (4px) on top of the container's px-2 (8px), so the header icon starts 12px from the card edge — while the child rows only had px-2 (8px). That 4px gap is the misalignment.

This bumps the child rows to px-3 (12px) so:

  • the child terminal icons sit directly under the header terminal icon, and
  • the trailing duration aligns under the header's chevron (also at 12px).

One-line change in apps/app/src/components/promptbox/banner/ThreadBackgroundCommandsCard.tsx.

Before / After

Before: header icon 12px from edge, child icons 8px → 4px off.
After: all icons 12px → aligned. Verified in the promptbox/banner/Background Commands Card Ladle story (the "multiple (expanded)" variant).

Tests

No automated test covers this purely-presentational className change; verified visually via the existing Ladle story.

🤖 Generated with Claude Code

The expanded background-commands list rows used px-2, but the header
row's terminal icon sits inside the toggle button which adds its own
px-1 on top of the container's px-2 — leaving the header icon 4px
further right than the child icons. Bump the child rows to px-3 so the
icons share the same left edge (and the trailing duration lines up
under the header chevron too).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@SawyerHood SawyerHood merged commit ad03315 into main Jun 19, 2026
6 checks passed
@SawyerHood SawyerHood deleted the fix/background-commands-icon-align branch June 19, 2026 21:15
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