emrg: task main table one-line layout — task-meta flex-basis:100% → flex:0 1 auto (rant 2026-08-20T10:34:40) - #879
Conversation
…lex:0 1 auto (rant 2026-08-20T10:34:40)
argszero
left a comment
There was a problem hiding this comment.
✅ LGTM — cycle (self-review). CI test + test-windows green (32325523343). Change is minimal: .task-meta flex-basis:100% → flex:0 1 auto; .task-row flex-wrap and .task-run-detail flex-basis:100% intentionally preserved; renderer-smoke CSS assertion added; pytest 986 passed + 1 skipped.
argszero
left a comment
There was a problem hiding this comment.
✅ LGTM — cycle (independent re-review). Head unchanged since 1st LGTM; CI test + test-windows still green (32325523343). Diff verified: .task-meta flex-basis:100% → flex:0 1 auto keeps the main table on one line while .task-run-detail retains flex-basis:100% for the expandable sub-table; smoke assertion added.
argszero
left a comment
There was a problem hiding this comment.
✅ LGTM — cycle (3rd consecutive, cycles 1130/1131/1132). Head unchanged, CI green. Merging.
Fix the GUI task management main-table layout regression reported by the host (rant 2026-08-20T10:34:40): each task card rendered as 3 lines instead of one compact row.
Root cause
.task-meta(components.css) usedflex-basis: 100%, forcing the "last run" metadata onto its own full-width line..task-rowisflex-wrap: wrap(added in emrg: persist task execution records to JSONL + fix task-row flex-wrap #876 for the expandable sub-table), so the actions (flex-shrink: 0) that no longer fit also wrapped to a third line.Fix
.task-meta:flex-basis: 100%→flex: 0 1 auto— content-sized, shares the row with the actions; wraps internally (flex-wrap: wrapretained) on narrow windows..task-rowkeepsflex-wrap: wrap;.task-run-detailkeepsflex-basis: 100%(expandable sub-table still renders below the card, not to the right).Verification
.task-metamust not containflex-basis: 100%and must beflex: 0 1 auto.