799858 - Firefox 16: Option to "Open Link in New Tab" does nothing

Status: RESOLVED FIXED

(WebExtensions :: General, defect)

Description

[Dave]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20100101 Firefox/15.0.1
Build ID: 20120905151427

Steps to reproduce:

Upgraded to Firefox 16. Did a Google search and tried to open a link by right-clicking and then selecting "Open Link in New Tab".


Actual results:

Nothing happens.


Expected results:

Link opens in new tab. Middle-clicking the link opens it in a new tab as normal.

Comment 1

[Olli Lehtinen]

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20100101 Firefox/16.0
Built from (about:buildconfig): http://hg.mozilla.org/releases/mozilla-beta/rev/a26a5447eaf9

Upgraded to Firefox 16 (beta channel) as well.

I can reproduce the failure when right-clicking a link and selecting "Open Link in New Tab". However, middle-clicking does work for me.

Comment 2

[Roberto]

Same thing happens to me on two different PCs

Comment 3

[Matthias Versen [:Matti]]

Please test if it works in the Firefox safemode: (alt key)/Help/restart with add-ons disabled

Comment 4

[Olli Lehtinen]

It works in safe mode. 

In addition, after running Firefox in safe mode it works in the normal mode as well! Makes me wonder...

Comment 5

[Loic]

You have surely an add-on which is incompatible with FF16 or partially compatible. If the issue is back, disable all the add-ons and renable them one by one to find the culprit.

Comment 8

[Quanah Gibson-Mount]

I have the same issue.  Control-T works to open a new tab.  Control+mouse click works to open a new tab.  Right click on link, and select to open a new tab does not.

Comment 9

[Loic]

(In reply to Quanah Gibson-Mount from comment #8)
> I have the same issue.  Control-T works to open a new tab.  Control+mouse
> click works to open a new tab.  Right click on link, and select to open a
> new tab does not.

Does it work normally in safe mode?

Comment 10

[Quanah Gibson-Mount]

After no-script addon updated, it started working again, so I think that is likely the addon that caused issues.

Comment 11

[Roberto]

(In reply to Quanah Gibson-Mount from comment #10)
> After no-script addon updated, it started working again, so I think that is
> likely the addon that caused issues.

No I don't think its NoScript because I don't have that AddOn. I only have Firebug and WebDeveloper.

Comment 12

[Matthias Versen [:Matti]]

Are there errors listed in the error console ?
Open the error console with ctrl+shift+j , select clear and use the "open link in a new tab" function when it doesn't work.

marking new for now

Comment 13

[u278084]

I came across this issue unexpectedly while browsing. Using Firefox 15.0.1 on xubuntu and have the following extensions enabled: Firebug, Safe, User Agent Switcher

Here is the errors that are showing up in the error console. This looks to be a Firebug issue:

Timestamp: 12-10-10 06:10:00 PM
Error: TypeError: PrefLoader is undefined
Source File: resource://firebug/prefLoader.js
Line: 123

Timestamp: 12-10-10 06:10:00 PM
Error: TypeError: gContextMenu is null
Source File: chrome://browser/content/browser.xul
Line: 1

Timestamp: 12-10-10 06:10:00 PM
Error: TypeError: gContextMenu is null
Source File: chrome://browser/content/browser.xul
Line: 1

Comment 14

[Kris Maglione [:kmag]]

Can anyone experiencing this issue attach the contents of about:support please?

Comment 15

[Jorge Villalobos [:jorgev] (he/him)]

There has been some feedback about this problem in the Mozilla Hispano channels, but nothing concrete about the cause of these problems.

Matt, have you seen anything about it on SUMO or Input?

Comment 16

[Jorge Villalobos [:jorgev] (he/him)]

Er, not sure why that flag was removed.

Comment 18

[Alex Keybl [:akeybl]]

Tracking for FF16, but given comment 11 and comment 13, this does not appear to actually be an in-product change.

Marcia - can you see if you can reproduce with the add-ons mentioned in this bug?

Comment 19

[Matt Grimes [:Matt_G]]

Hey Jorge. I found this on SUMO: https://support.mozilla.org/en-US/questions/939088

It looks like it might be Firebug causing it. We'll need to confirm though. Let me know if there is anything else you need from my end.

Comment 20

[Kris Maglione [:kmag]]

If restarting fixes the problem, my guess is that the live update of Firebug is the cause.

Comment 21

[Quanah Gibson-Mount]

Hm, I have to say after firebug updated, is when I restarted (and then noscript updated in that new session).  So it definitely could have been firebug, since I did restart after that to try other things, and it was fixed.

Comment 22

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Yes, this is related to restart-less Firebug update. You need to restart Firefox to fix the problem. The underlying issue is fixed in Firebug 1.10.4
Honza

Comment 23

[Jorge Villalobos [:jorgev] (he/him)]

Okay, so I guess there's nothing else to do here. Affected users just need to restart their browsers in order to correct the problem, and the new version of Firebug shouldn't display this problem anymore.