The Live activity card renders only its first column. The Task, Detail and When <th>s are laid out at zero width, and every body row spans the full card width, so the feed reads as a flat list of event names.
Seen on a live instance once the feed carried grouped rows (curator_run ×6, curator_action ×17, stage_finish ×10 interleaved with singletons). An earlier capture of the same card from a quieter feed rendered all four columns correctly, so the collapse correlates with the grouped rows rather than being permanent.
The markup is structurally correct and is not the cause: LiveActivityCard.vue emits four <TableHead>, and ActivityRow.vue is a single-root <TableRow> with four <TableCell>. Table.vue renders a real <table> with no table-fixed, so this is a width computation in the auto table layout, not a DOM-shape fault.
Prime suspect is the Detail cell's w-[55%] max-w-0 with a truncate span inside (present in both the group row and ActivityRow): max-width: 0 caps that column's max-content contribution at zero, and the group rows now supply a much longer representative detail string than the singles did. Worth confirming against the live card before changing it.
Imported from beads archie-core-cpkh · GitHub #1239 · type bug · priority P3 · created 2026-10-05
The Live activity card renders only its first column. The Task, Detail and When `<th>`s are laid out at zero width, and every body row spans the full card width, so the feed reads as a flat list of event names.
Seen on a live instance once the feed carried grouped rows (`curator_run ×6`, `curator_action ×17`, `stage_finish ×10` interleaved with singletons). An earlier capture of the same card from a quieter feed rendered all four columns correctly, so the collapse correlates with the grouped rows rather than being permanent.
The markup is structurally correct and is not the cause: `LiveActivityCard.vue` emits four `<TableHead>`, and `ActivityRow.vue` is a single-root `<TableRow>` with four `<TableCell>`. `Table.vue` renders a real `<table>` with no `table-fixed`, so this is a width computation in the auto table layout, not a DOM-shape fault.
Prime suspect is the Detail cell's `w-[55%] max-w-0` with a `truncate` span inside (present in both the group row and `ActivityRow`): `max-width: 0` caps that column's max-content contribution at zero, and the group rows now supply a much longer representative detail string than the singles did. Worth confirming against the live card before changing it.
---
_Imported from beads `archie-core-cpkh` · GitHub #1239 · type bug · priority P3 · created 2026-10-05_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The Live activity card renders only its first column. The Task, Detail and When
<th>s are laid out at zero width, and every body row spans the full card width, so the feed reads as a flat list of event names.Seen on a live instance once the feed carried grouped rows (
curator_run ×6,curator_action ×17,stage_finish ×10interleaved with singletons). An earlier capture of the same card from a quieter feed rendered all four columns correctly, so the collapse correlates with the grouped rows rather than being permanent.The markup is structurally correct and is not the cause:
LiveActivityCard.vueemits four<TableHead>, andActivityRow.vueis a single-root<TableRow>with four<TableCell>.Table.vuerenders a real<table>with notable-fixed, so this is a width computation in the auto table layout, not a DOM-shape fault.Prime suspect is the Detail cell's
w-[55%] max-w-0with atruncatespan inside (present in both the group row andActivityRow):max-width: 0caps that column's max-content contribution at zero, and the group rows now supply a much longer representative detail string than the singles did. Worth confirming against the live card before changing it.Imported from beads
archie-core-cpkh· GitHub #1239 · type bug · priority P3 · created 2026-10-05