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

(#902) Bug Closed: Fixed messaging ui

Reproduction steps

  1. hover over any message in a channel
  2. notice there is no quick context menu (apologies, I'm not sure what the actual term is!)
  3. right click on message
  4. quick context menu appears, but is not interactable, as the full context menu is now open

Observed behaviour

When hovering over a message, the quick access to replying, forwarding, or reacting to a message does not show up in the upper right corner of the highlighted message. Right clicking for the full menu displays this quick access bar, but it is not interactable and disappears upon closing the right-click menu. This behavior is also found on the Firefox web app on the same computer. image image

Build information

Stable Desktop 2026.1003.155758, Web 2026.1003.184210, Windows 11 10.0.26200 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US

Platform

macOS, Windows, Linux

  1. The pull request fluxer#4136 mentions this post Merged

6 comments

Sign in with Fluxer to comment and vote.
Comment by Rex
RexSystem 1 vote
Status changed from Needs triage to Fixed
Fixed in fluxer#4136. The fix is live in web release 2026.1115.234056.
Comment by @rexgoldenglitz
RexSystem 2 votes originally by @rexgoldenglitz on GitHub OP
update, restarting my laptopdid nothing to affect this bug (as I imagined but figured I'd do anyway just since it's easy to check). I'm also on windows 25h2 on this device rather than 26h2, if that helps.
Comment by Hampus
HampusStaff 1 vote originally by @hampus-fluxer on GitHub 1 reply
I can't repro this myself on the same client details as you, very peculiar. If anyone can repro let me know, it might depend on custom CSS that you've applied to, but I guess you haven't applied a custom theme?
Comment by mangafan
Hi Hampus, I added a separate comment in this bug (not this comment), perhaps it could have one key to repro.
Comment by @rexgoldenglitz
RexSystem 1 vote originally by @rexgoldenglitz on GitHub OP
No custom CSS added! I just started using the app today. I'm in the process of doing some backups so I can't restart my PC yet, but I'll restart my desktop ASAP and see if that alters anything. Does the aspect ratio of my monitor come into play here? It's a 16:10 monitor with 2560×1600 resolution. It's set at 150% scale normally but the effect is replicated at 125% and 100% scale as well.
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.