mouse4 or mouse5 set to PTT does not disable navigation using these buttons

(#800) Bug Open: Confirmed Priority: P2 desktop voice

Reproduction steps

  1. Activate Push to Talk
  2. Bind either mouse4 or mouse5 as the Push-to-Talk (PTT) key.
  3. Join a voice channel
  4. If mouse4 is the PTT key, navigate backwards first by hitting mouse5.
  5. With Fluxer as the active window, activate PTT.
  6. Observe that mouse4 navigates forward and mouse5 navigates backwards in the Fluxer app.

Observed behaviour

When using PTT, it is not desirable that your PTT key also performs forward and backward navigation in the app. A simple solution is to either detect that mouse4 and/or mouse 5 have been bound and disable these, or provide a global 'disable mouse navigation' toggle option.

Build information

Canary Desktop 2026.829.130244, Web 2026.829.153624, Linux 7.1.11-arch1-1 (x64), Electron 42.10.0, Chrome 148.0.7778.280, Node 24.18.1, Locale en-US

Platform

macOS, Windows, Linux

3 comments

Sign in with Fluxer to comment and vote.
Comment by bizo
bizoReviewer 1 vote
Status changed from Needs triage to Confirmed
CR: Canary Desktop 2026.1009.45608, Web 2026.1009.142425, Windows 11 10.0.26200 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-GB
Comment by septicity
septicity 2 votes originally by @Septicity on GitHub 1 reply
Noting for extra context: The issue is unrelated to PTT; mouse4 and mouse5 have hard-coded back and forward controls that work simultaneously with custom keybinds.
Comment by fltx
fltx 1 vote
There should be a way to disable this though. It is very difficult to even bind mouse4 and mouse5 to PTT, because doing so takes you out of the screen. A user who also uses push to talk on mouse4 also probably doesn't want to be navigated out of the channel they are in every time they wish to speak. I don't see why this should be hard coded.