1272140 - Middle Click Opening New Windows Instead of New Tabs

Status: RESOLVED INCOMPLETE

(Firefox :: Tabbed Browser, defect)

Description

[slumbergod]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0
Build ID: 20160502172042

Steps to reproduce:

Using FF 46.01 on Xubuntu 16.04

Middle click a link on a page


Actual results:

It opens a new tab but then the new tab disengages itself from the main Firefox window to open a new Firefox window


Expected results:

The tab should open in the main window not spawn a new one.

This issue does not happen everytime I middle click a link, just often enough that it is annoying me. When I roll back to 45.02 the problem goes away. Upgrade back to 46.01 the problem returns.

Comment 1

[Loic]

46 supports Gtk3 now, it could be an issue with that.

Comment 2

[08xjcec48]

I'm affected by this too using Ubuntu 16.04 and Plasma 5.7.

Comment 3

[slumbergod]

I think it's going to be one of those bugs that never gets fixed because it isn't affecting everyone.

There is an addon which fixes the bug though. Try this:
"bug489729(Disable detach and tear off tab)"
https://addons.mozilla.org/en-US/firefox/addon/bug489729-disable-detach-and-t/

Comment 4

[Karl Tomlinson (:karlt)]

I don't have any ideas how a switch from gtk2 to gtk3 would cause a new tab to become a new window (and this doesn't happen for me).  Moving to Firefox product for now to see if some engineers can suggest some diagnostics to collect.

Comment 5

[:Gijs (he/him)]

Questions:

- which window managers do you use?
- when you say "middle click", physically speaking is that button also the scrollwheel on your mouse?
- does this also happen if you use ctrl-click ?
- is it correlated with specific pages / links at all, or does it just seem to be random?

Comment 6

[08xjcec48]

@:Gijs Kruitbosch I believe that my own problem is better covered by #489729 .

Comment 7

[Jared Wein [:jaws] (please needinfo? me)]

Closing the bug as incomplete and clearing the needinfo request due to lack of response from the reporter. Please reopen the bug and include a response to comment #5 if you can still reproduce the bug.