Closed Bug 1645999 Opened 5 years ago Closed 5 years ago

Mousebutton 4 and 5 does not seem to work (are instead interpreted as mousebutton 3)

Categories

(Core :: Widget: Cocoa, defect)

77 Branch
defect

Tracking

()

RESOLVED DUPLICATE of bug 1615213

People

(Reporter: eirik, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:77.0) Gecko/20100101 Firefox/77.0

Steps to reproduce:

  • Install latest Firefox (77.0.1) on MacOS (Catalina 10.15.5)
  • Navigate to any website and click mousebutton 4 or 5
  • Buttons do not function as back/forward, but rather produce a scroll wheel like mousebutton 3
  • Try to search for "mousebutton.4th.enabled" and "mousebutton.5th.enabled" in "about:config", but cannot find any such settings
  • Try to add them manually and setting them to "true" -> no effect even after restarting Firefox

Expected results:

IMO mousebutton 4 and 5 should be enabled by default (functioning as back/forward). At the very least there should be settings to enable/disable them in "about:config" as some Google results suggest have existed before?

Someone gave me a tip about this: https://github.com/archagon/sensible-side-buttons

Installing that fixed it for me. Would be great if that wasn't necessary though...

Hi Eirik,

I will move this over to a component so developers can take a look over it and see if it's possible to add the settings to enable them. If is not the correct component please feel free to change it to an appropriate one.

Thanks for the report.

Best regards, Clara.

Component: Untriaged → Preferences: Backend
Product: Firefox → Core

The severity field is not set for this bug.
:njn, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(n.nethercote)

This is not a libpref bug. Maybe "Widget: Cocoa" is a more appropriate component?

Component: Preferences: Backend → Widget: Cocoa
Flags: needinfo?(n.nethercote)
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.