Skip to content

fix(v2): connector line 1 and gate pod names wrap instead of ellipsising at 390 - #1567

Merged
lilyshen0722 merged 2 commits into
mainfrom
wren/connectors-390-clips
Sep 6, 2026
Merged

lilyshen0722 merged 2 commits into
mainfrom
wren/connectors-390-clips

Conversation

@lilyshen0722

Copy link
Copy Markdown
Contributor

Follow-up to #1557, offered in the pod when the 390 capture was posted (64144).

Two clips at 390, both older than the page PR and neither on the meta line:

  • the unavailable row's first line (Not yet. Tell us which channel you need…) ended in an ellipsis
  • a long pod name in the gate list clipped to Rewire Live…

Both now wrap. The system rule is the one lily-shen set for meta on #1557: shorten or wrap to two lines, never an ellipsis. .v2-connector-row__details strong and .v2-connector-gate__pod drop nowrap + text-overflow and gain overflow-wrap: anywhere; the mark stays centred beside a two-line pod name.

v2-layout-invariants.test.ts pins both rules (no nowrap, no text-overflow, wrap present) the way it already pins .v2-connector-row__detail.

Verified in a real browser at 390 and 1440 with a 39-character pod name and the full not-yet sentence: no element reports scrollWidth > clientWidth; both wrap to two lines. Captures in the pod thread. Tests: 128 pass across the two suites; tsc --noEmit clean.

🤖 Generated with Claude Code

…ing at 390

Two clips visible in the 390 capture of #1557 (64144): the unavailable row's
first line ended in an ellipsis, and a long pod name in the gate list clipped
to "Rewire Live…". Both predate the page PR; neither is meta, but the same
system rule applies — shorten or wrap, never an ellipsis. Line 1 and the pod
name now wrap under the mark; the invariants test pins both rules the way it
already pins the meta line.
@lilyshen0722
lilyshen0722 merged commit 5d87cb6 into main Sep 6, 2026
14 checks passed
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