Skip to content

fix(desktop): keep hover action bar on-screen for long-token messages#1079

Open
wesbillman wants to merge 1 commit into
mainfrom
brain/dm-reaction-bar-offscreen
Open

fix(desktop): keep hover action bar on-screen for long-token messages#1079
wesbillman wants to merge 1 commit into
mainfrom
brain/dm-reaction-bar-offscreen

Conversation

@wesbillman

Copy link
Copy Markdown
Collaborator

Problem

Hovering a message whose body contains a long, unbreakable token (e.g. a long
URL) pushes the hover action bar off the right edge of the window, making
reactions/reply unreachable. Reported in #reactions-broken-in-dms.

The long token widens the message row past the timeline. The timeline clips
horizontal overflow, and the action bar is anchored to the row's right edge —
so the bar gets dragged off-screen with the row (worst seen: +157px past a
1280px window).

Fix

Add overflow-wrap: anywhere to message paragraphs so long tokens wrap. The
row stays within the timeline and the bar stays reachable.

Verification

  • New Playwright regression (message-action-bar-overflow.spec.ts) asserts the
    bar's right edge stays inside the window at 1280/1024/900px. It fails on
    main
    (action bar right edge off-screen at width 1280) and passes with
    this change
    .
  • typecheck, lint (changed files), and the e2e test all pass.

Before

Long URL overflows the row; no action bar visible on hover.

After

URL wraps; full action bar (👍 ❤️ 😂 🎉 + emoji/reply/more) renders inside the window.

(Before/after screenshots posted in #reactions-broken-in-dms.)

Wrap long unbreakable tokens in rendered message paragraphs so markdown content cannot widen a message row past the timeline and push the hover action bar off-screen.

Co-authored-by: Pinky <44b8e82baa6e0e254e0208d68f335c283c94e7b78dd1fa10d5a49d3f13dd0435@sprout-oss.stage.blox.sqprod.co>
Signed-off-by: Wes <wesbillman@users.noreply.github.com>
@wesbillman wesbillman force-pushed the brain/dm-reaction-bar-offscreen branch from 366d85e to 8372e2c Compare June 17, 2026 04:22
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