[Bug]: Wide chat mode opens minimap preview over text and blocks selection #16447

Activity

1. juliusmarminge commented on Oct 6, 2026

   

   juliusmarminge

   on Oct 6, 2026

   Member

   More actions

   Note

   Grok responding on behalf of Julius.

   Triage

   Thanks @MaximilianMauroner for the screenshots and for filing this separately from #3702. The Wide-mode report lines up with the current code.

   What I found

   • Reading the code on main (9bd1d8009a), this looks like a new path rather than a reopen of [Bug]: Timeline minimap hover target extends into text content area at non-default zoom levels #3702. That issue was closed by fix(web): scope timeline minimap hover target to the side gutter #3869, which caps the collapsed minimap strip to the side gutter so it doesn't sit on the message column. The open preview kept a fixed-width target, and the Chat width setting from feat(web): add chat width setting for wide screens #11594 is what makes that target land on the text.
   • The collapsed strip is still gutter-capped. resolveTimelineMinimapHitStripWidth measures the rendered column ([data-timeline-root], .chat-content-lane) and keeps the hit area between left-3 and the column, or disables it when the gutter is too small. Wide mode doesn't change that.
   • Opening a mark does. resolveTimelineMinimapInteractiveWidth switches the same element to a fixed 22rem whenever a preview is open, for the full height of the rail. The preview card is left-8 w-80 inside that box (TimelineMinimap in apps/web/src/components/chat/MessagesTimeline.tsx). The rail button fills the box, and its mousedown calls preventDefault() except on the preview itself, so the message underneath can't start a selection. mouseleave only fires after the pointer leaves the whole 22rem area, so brushing the strip keeps the card up while the pointer is over the text.
   • Wide sets --chat-content-max-width to 72rem. The preview box runs from 12px to about 364px, and the column's left edge is (pane − 1152px) / 2, so on a timeline pane narrower than about 1880px the open card and its hit target cover the message. That matches the screenshots. Comfortable (46rem) only hits this under about 1464px, which is why it shows up with Wide. Full width measures a zero gutter, so the strip stays pointer-events-none and this path shouldn't open. Comfortable and Full weren't checked in a running client, and there's no minimap on mobile.

   Likely fix area

   Some options, keeping the collapsed strip gutter-capped either way:

   • When a preview is open, limit pointer events to the strip plus the card (and a short bridge between them) instead of stretching the full-height rail to 22rem across the column.
   • Dismiss the preview when the pointer moves onto the message, so the text can be selected.
   • A 20rem card can't fit in a Wide gutter, so it may still paint over the column. One option is to let it paint there without owning the pointer.

   A maintainer will decide on the fix direction.
2. juliusmarminge

   added

   bugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.

   via-triageFiled through npx t3 triageFiled through npx t3 triage

   on Oct 6, 2026