Hovering over message does not generate reply/forward/emote context menu

(#902) Bug Closed: Fixed messaging ui

Thread

Comment by mangafan
Title: Message hover toolbar never appears on touchscreen laptops (CSS hides it under pointer: coarse)

Symptom

  • Hovering a message with the mouse shows the grey hover background but not the action bar (quick reactions, edit, reply, forward, thread, more).
  • Right-clicking the message makes the action bar appear at the top right while the context menu is open; it disappears when the menu closes.
  • Desktop app on Windows 10, touchscreen convertible laptop used with a mouse/trackpad. Same symptom as this post (#902): that reporter also had a 2560x1600 laptop on Windows 11 and saw it in Firefox too.

Root cause (read from fluxerapp/fluxer main, 2026-10-22)

  1. Windows reports convertible laptops as "slate mode" (SM_CONVERTIBLESLATEMODE = 0) whenever the slate indicator or the registry override says so. Chromium's IsDeviceUsedAsATablet() then returns true and the browser answers (pointer: coarse) and (hover: none) with true, even though a mouse is in use. Verified on my machine:
    matchMedia('(pointer: coarse)').matches  // true
    matchMedia('(any-hover: hover)').matches // false
  2. fluxer_app/src/features/channel/components/MessageActionBar.module.css lines 26-32:
    @media (pointer: coarse) {
      :global([data-flx-action-bar]:not([data-flx-action-bar-forced])) .actionBarContainer:not(:has(:focus-visible)) {
        opacity: 0; visibility: hidden; pointer-events: none;
      }
    }
    This hides the bar for every "coarse pointer" device unless the message is "forced".
  3. ChannelMessage.tsx lines 680-684:
    isActionBarForcedVisible = isKeyboardFocused || contextMenuOpen || isPopoutOpen
    That is why a right-click (contextMenuOpen via useContextMenuHoverState) makes the bar show, and why it vanishes when the menu closes.
  4. Hover itself still works: MessageHoverTracking.ts sets the hover state from pointer events and already ignores pointerType === 'touch' (lines 86-87). So the media query protects no touch user; it only hides the bar from mouse users whose OS reports a tablet.
  5. Since PRs #2761 / #2798 / #3337 there is no CSS :hover fallback, so this one rule decides.

Why it could not be reproduced

It needs a device where the OS reports tablet mode: touchscreen convertibles, 2-in-1s, Surface-style devices, or any Windows machine with the ConvertibleSlateMode registry override set to 0. On a normal desktop pointer: coarse is false.

Suggested fix

  • Remove MessageActionBar.module.css lines 26-32. The JS tracker already handles touch.
  • If hiding on touch is still wanted, key it on the last real input instead of a media query: have MessageHoverTracking set html[data-flx-last-pointer="touch"] on a touch pointerdown and clear it on a mouse/pen pointermove, then use that attribute in the CSS.
  • Switching the query to (any-hover: hover) would not help; on an OS-reported tablet it is false as well.

Workaround for affected users (Theme Studio quick CSS, tested)

@media (pointer: coarse) {
  html:is(.window-focused, .unfocused-fully-interactive):not(.window-focus-activation-guard)
    [data-flx-action-bar][data-flx-action-bar-active]
    [data-flx="channel.message-action-bar.message-action-bar-core.action-bar-container"] {
    opacity: 1 !important; visibility: visible !important; pointer-events: auto !important;
  }
}

Quick check for anyone

Open devtools in Fluxer and run matchMedia('(pointer: coarse)').matches. true = affected.