Run bar: in a half-width window, the run's time is drawn over the state chip #314

Closed
opened 2026-10-29 17:53:09 -04:00 by cmoriarty · 1 comment
Owner

What happens
At 841 px wide (a window halved), run 147's bar draws the run's time over the ● Running chip (chip x 508-583, time 569-614), and the chip looks cut off. From 1000 px up nothing overlaps.

The title block's floor (md:min-w-[26rem]) was sized for a stub of the repository's name, the pipeline, ten characters of title and the chip. Since #172 the breadcrumb also carries the apply line (auto: one step (400k context)), and the breadcrumb never shrinks: it has no min-w-0, so its minimum is its whole text (372 px at every width). The block's content outgrows its floor, the row doesn't wrap, and the controls cover the chip.

Fix
min-w-0 on the breadcrumb, so the apply line and then the repository's name give way, as its comment says. Check the floor against the narrowest content with the apply line shown.

Done when
At 841 px the chip is whole and nothing overlaps, and a browser spec checks at a narrow width that the chip and the controls don't meet.

**What happens** At 841 px wide (a window halved), run 147's bar draws the run's time over the `● Running` chip (chip x 508-583, time 569-614), and the chip looks cut off. From 1000 px up nothing overlaps. The title block's floor (`md:min-w-[26rem]`) was sized for a stub of the repository's name, the pipeline, ten characters of title and the chip. Since #172 the breadcrumb also carries the apply line (`auto: one step (400k context)`), and the breadcrumb never shrinks: it has no `min-w-0`, so its minimum is its whole text (372 px at every width). The block's content outgrows its floor, the row doesn't wrap, and the controls cover the chip. **Fix** `min-w-0` on the breadcrumb, so the apply line and then the repository's name give way, as its comment says. Check the floor against the narrowest content with the apply line shown. **Done when** At 841 px the chip is whole and nothing overlaps, and a browser spec checks at a narrow width that the chip and the controls don't meet.
Author
Owner

Confirmed on production (1fc0f22, PR #319); closing. Run 152 (thorough, with the apply line auto: one step (400k context)) at 841 px wide: the breadcrumb gives way, 16-252 px where it was 16-388, and the state chip (372-447) meets neither the run's time (459-504) nor the controls (512-825). At 1000 and 1200 px the breadcrumb is whole, as before.

**Confirmed on production (1fc0f22, PR #319); closing.** Run 152 (thorough, with the apply line `auto: one step (400k context)`) at 841 px wide: the breadcrumb gives way, 16-252 px where it was 16-388, and the state chip (372-447) meets neither the run's time (459-504) nor the controls (512-825). At 1000 and 1200 px the breadcrumb is whole, as before.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#314
No description provided.