You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(planning): fix interview id-chip wrapping, Summary table word breaks and header height at 390 px #8085
Type: Bug Summary: At phone width, id chips and Summary table words stay whole, and the question title shows in the first screen.
Current behavior:
The id chip style lets a chip break anywhere, so an id splits across lines: in Activity at 425 px and in Notes at 390 px.
At 390 px the Summary Decisions table breaks words mid-word.
At 390x844 the header is 244 px tall and pushes the question title below the first screen.
Desired behavior:
An id or id range such as Q12 or Q4-Q9 never splits across lines. A chip holding several ids may wrap between ids.
Summary Decisions table cells wrap only at word boundaries. A token too long for its cell scrolls inside the table's own container, never the page.
At 390x844, after load, the question title is fully visible with no scrolling.
Layout at 1440 px is unchanged.
Key interfaces:
The id-chip style (the chip inside question meta, Activity and Notes).
The Summary Decisions table.
The header under the phone breakpoint.
Acceptance criteria:
The diff adds a UI check at 390x844 and at 425 px: every id chip in Activity and Notes renders each id on one line.
The diff adds a UI check at 390 px: no Summary Decisions table cell has a computed word-break: break-all or overflow-wrap: anywhere, and the document has no horizontal scroll.
The diff adds a UI check at 390x844: the question title's bounding box bottom is at most 844 with scroll at 0.
scripts/check-changelog-fragments.sh passes, with one planning patch fragment added.
CI's test-bash passes on the PR.
Out of scope:
Flyout overlap and Notes collapsing (sibling items).
This was generated by AI during backlog shaping. Split from #7756 so each piece fits the lane's run time; the owner approved this split in an attended backlog-shaping session on 2026-10-18.
Activity