Can't 'Open in new tab' while new page is loading (ctrl + T) works

UNCONFIRMED
Unassigned

Status

()

Firefox
Tabbed Browser
UNCONFIRMED
2 years ago
2 years ago

People

(Reporter: michaelpittino, Unassigned)

Tracking

40 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150826023504

Steps to reproduce:

Looking for something at google - clicking on a link (page starts to load..) while the page loads I clicked on another link (rightclick -> open in new tab).


Actual results:

Nothing happened - firefox loaded the page I selected first and no new tab was opened.


Expected results:

The page should be opened and loaded. (Ctrl + T) works.

Comment 1

2 years ago
Is it reproducible?
If yes, could you test with a clean profile, please.
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
Component: Untriaged → Tabbed Browser
Flags: needinfo?(michaelpittino)
(Reporter)

Comment 2

2 years ago
Yes this is reproducible, even with a clean profile.
I noticed that this only happens on the google search results page, not on other pages.
Flags: needinfo?(michaelpittino)

Comment 3

2 years ago
Where do you click on the 2nd link? Is it a Google result or link from the 2nd tab loading?

I tried on my side on a Google result page and I can open many tabs with middle click or the context menu.
(Reporter)

Comment 4

2 years ago
Maybe I explained it too bad:
1) I go on google.com
2) I search for "Some foobar test"
3) I click on search result #1 (normal leftclick)
4) While search result #1 page loads (the google search results page is still visible) i click on search result #2 (rightclick -> open in new tab)
5) nothing happens

But Ctrl + Leftclick works (opens new tab while loading page)

Comment 5

2 years ago
Step 3) open the result in the current tab on my side, leftclik doesnt open any tab, it just load the link in the current tab.
You need to log in before you can comment on or make changes to this bug.