748226 - "open link in new window" URL is not shown in address bar

Status: RESOLVED WORKSFORME

(Firefox :: Untriaged, defect)

Description

[[e-mail]]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20100101 Firefox/11.0
Build ID: 20120312181643

Steps to reproduce:

Windows 7 Firefox 11 (did this for several versions before 11 too)
Simply...
hover over a link on a web page.
right click for context menu, select:
"open link in new window"


Actual results:

When the new window opens from the link clicked, the URL is NOT displayed in the address bar, it remains blank.


Expected results:

When the new window opens from the link clicked, the URL should be displayed in the address bar.

Comment 1

[[e-mail]]

open link in new window, context menu, URL, new window

Comment 2

[Shorty]

I can confirm this also happens in Firefox 12. Another probably related problem is when you click on "New Window" and use your Bookmarks to open a URL, the URL does not appear on the address bar, and you can't use the "Reload" button.

Comment 3

[Richard Kellogg]

I am using Firefox 15.0.1 with Win7 (64-bit).  This bug is a major annoyance for me and getting it fixed is my #1 priority for FF.  The bug happens consistently and is easily reproducible.

Additional steps:  If you do <shift> + <left click> on a link, you also get a new window with the URL missing from the address bar.

Note however, if you:
   hover over a link on a web page.
   right click for context menu, select:
   "open link in new Tab" 
the tab appears with the URL shown correctly.

Note also, when URL is missing, you cannot copy the URL to the Windows clipboard.  But if you bookmark that page, the URL suddenly appears in the address bar and you can then copy it to the clipboard.

Comment 4

[Stefan Weiss [:sir_none]]

Hello,

I just found this old bug report and after some tests it looks OK to me in actual version of Firefox.
can you please confirm it from your site? or give us as many details as possible to reproduce it.

thanks for your help.

Comment 5

[Richard Kellogg]

I am now using Firefox 32.0.3, and the steps in my 2012-09-16 post no longer reproduce the error.  It looks like one or more of the updates have fixed it.  I recommend changing the bug report to "resolved".  Thanks.