Skip to content

Chat: a mid-width pane starts the nick column at 9ch, not 12ch - #147

Merged
rdrake merged 1 commit into
evilnet:developfrom
rdrake:fix/nick-column-mid-width
Nov 2, 2026
Merged

rdrake merged 1 commit into
evilnet:developfrom
rdrake:fix/nick-column-mid-width

Conversation

@rdrake

@rdrake rdrake commented Oct 31, 2026

Copy link
Copy Markdown
Collaborator

On a desktop window of modest width, such as the Tauri shell's default 1100px at the default text size, the nick column kept its full 12ch while the text still had room. Short nicks are right-aligned, so they stood well apart from their timestamps with a band of empty space in between.

What

A container query on #chat: once the widest time column (10.5ch), the full nick column (12ch) and 50 characters of text no longer fit in the pane, the nick column starts at its 9ch floor instead of 12ch.

  • A nick longer than 9 characters gets the ellipsis sooner.
  • The floor is unchanged, so the user-list overlay and inline-flow thresholds that depend on it don't move.
  • Wide panes and the phone's inline layout are unaffected.

Testing

  • tools/scenarios/message-gutter.mjs passes, all 40 checks across font sizes and widths.
  • At 1100×760, default text size: the nick column goes from 170px to 132px, and the text gains 37px.

On a desktop window of modest width (the Tauri shell's 1100px default, at
the default text size) the nick column kept its full 12ch while the text
had room to spare, so short nicks stood off from their time across a
band of empty space. Below the width where the widest time column, the
full nick column and 50 characters of text fit, the column starts at its
9ch floor instead; a longer nick takes the ellipsis sooner. The floor,
and with it the user-list and inline-flow thresholds, are unchanged.
message-gutter.mjs passes; at 1100x760 the column goes from 170 to 132px.
@rdrake
rdrake force-pushed the fix/nick-column-mid-width branch from 234f905 to fce891d Compare November 2, 2026 20:17
@rdrake
rdrake marked this pull request as ready for review November 2, 2026 20:26
@rdrake
rdrake merged commit e1b1c27 into evilnet:develop Nov 2, 2026
1 check passed

This branch was successfully deployed

1 active deployment
github-pages — fce891de Deployed Nov 2, 2026 by rdrake via deploy #471
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