Software used:
Firefox ESR 102.15.1 on RedHat Enterprise Linux 8 with the Xfce4 desktop environment in version 4.16.3.
I run two Firefox windows on two different virtual… (read more)
Software used:
Firefox ESR 102.15.1 on RedHat Enterprise Linux 8 with the Xfce4 desktop environment in version 4.16.3.
I run two Firefox windows on two different virtual desktops. Most open tabs in each of them are tied to the workflow I use on each desktop, in case this is somehow important.
Problem description:
Sometimes, Ctrl+clicking on HTTP or HTTPS links will open the resource in a new window instead of in a new tab. This appears to be random, and does not depend on the link target. It is also not properly reproducible, so the same link may work just fine and open the resource in a new tab as expected on another attempt to Ctrl+click it.
Properties like browser.link.open_newwindow or browser.link.open_newwindow.override.external are unmodified and set at their default values.
I can drag the new window's only tab back into the browser window in which I originally clicked on such a link, but this is becoming tedious. Sometimes I overlook this, resulting in a chaos of multiple open Firefox windows with multiple open tabs in each of them.
The behavior I would expect:
When Ctrl+clicking on links, their resources should always open in a new tab, never in a new window, unless it's a link with a protocol that Firefox by itself won't handle and where it will have to rely on another program to open it (e.g. ftp://, ssh:// or mailto:somebody@somedomain.com).
My request:
I would like this to be fixed if it's a real bug. If I am somehow responsible myself without knowing why, please just let me know what I might be doing wrong.
If there are some workarounds for this, e.g. some properties I could set in about:config, help with those would be appreciated as well.
Most information I can find about similar problems is pretty old by now and pre-dates Firefox 102.15.1 by many releases and years. All suggestions I could find about what one would need to change in about:config to fix this seem to be the default by now anyway.
Thank you very much!