Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Learn More

Scroll wheel click on links to open in new tab

  • 3 отговора
  • 0 имат този проблем
  • 1 изглед
  • Последен отговор от 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.

Избрано решение

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.

Прочетете този отговор в контекста 👍 0

Всички отговори (3)

more options

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

What OS?

Променено на от 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)

Променено на от Andrew.Barge

more options

Избрано решение

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.