Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Learn More

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Scroll wheel click on links to open in new tab

  • 3 antwurd
  • 0 hawwe dit probleem
  • 854 werjeftes
  • Lêste antwurd fan Andrew.Barge

more options

Previous versions of Firefox allowed scroll wheel button clicking to open links. I noticed that the latest version doesn't allow this. Ctrl + left click works as normal but not the scroll wheel clicking.

Previous versions of Firefox allowed scroll wheel button clicking to open links. I noticed that the latest version doesn't allow this. Ctrl + left click works as normal but not the scroll wheel clicking.

Keazen oplossing

I was able to resolve this by plugging in another mouse to confirm middle click does work so it was my original mouse that was the issue. Unplugging it and plugging it back in restored functionality. Incredibly weird but this is resolved now.

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (3)

more options

Firefox has support for a middle-click paste feature. about:config => middlemouse.paste

What OS?

Bewurke troch jonzn4SUSE op

more options

middlemouse.openNewWindow is by default true. This means clicking the mouse mouse on a link should open it in a new tab. This is also reflected in the shortcuts listed here:

"Open Link in New Background Tab" has Ctrl + Left-click Link and Middle-click Link as the options. Expected outcome was a new tab being opened. Instead nothing is happening.

https://support.mozilla.org/en-US/kb/mouse-shortcuts-perform-common-tasks?redirectslug=Mouse+shortcuts&redirectlocale=en-US

This is on Ubuntu 22.04 => Firefox 108.0.2 (64-bit)

Bewurke troch Andrew.Barge op

more options

Keazen oplossing

I was able to resolve this by plugging in another mouse to confirm middle click does work so it was my original mouse that was the issue. Unplugging it and plugging it back in restored functionality. Incredibly weird but this is resolved now.