• 1 vote

    Update: source of the bugs has been found.

    I investigated this further with LLM assistance. I know you guys will not review LLM code, but hopefully the investigation's results themselves will be helpful. The attached ZIP contains a proposed patch (feel free to ignore this), explanations with source files/line numbers, and before/after code snippets. I can reproduce both problems in the desktop client:
    • Home/End near custom emoji: the caret disappears and typing stops. After Home, copying the draft confirms the typed letters aren’t there.
    • Left after a line-start emoji: type hello, Shift+Enter, insert a custom emoji, then press Left and type X. X appears on the previous line instead of before the emoji.
    Right arrow works normally in my tests, with or without the trailing space. The proposed patch passes isolated Lexical tests, but hasn’t been tested in a complete Fluxer build. The included HTML is only a browser experiment, not an exact Fluxer reproduction. Could someone review the patch and test it in the full client?
  • 1 vote
    I've updated this bug with findings on why the bugs exist and also LLM-suggested solutions. I understand that you guys won't review LLM generated code, and I understand why, and I'm not suggesting you do. I'm simply providing all of the information I have in case any of it can be of help. Since the source of the bugs have been identified though, I will not make any new bug reports or edit this one significantly besides adding the zip.
  • 1 vote
    okay, i guess i'll close this one and make 2 new bug reports then. give me a bit of time though. and just in case, i updated the desktop client to Stable Desktop 2026.1025.12517 and B was still an issue.
  • 1 vote
    Same for End key.
  • 1 vote
    Hi Hampus, I added a separate comment in this bug (not this comment), perhaps it could have one key to repro.
  • 1 vote
    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.