Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

Scroll wheel click on links to open in new tab

  • 3 amsoshi
  • 0 sa na da wannan matsala
  • 1238 views
  • Amsa ta ƙarshe daga 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.

Mafitar da aka zaɓa

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.

Karanta wannan amsa a matsayinta 👍 0

All Replies (3)

more options

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

What OS?

An gyara daga jonzn4SUSE

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)

An gyara daga Andrew.Barge

more options

Zaɓi Mafita

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.