Closed
Bug 265704
Opened 20 years ago
Closed 20 years ago
Opening a link in a new tab results in a blank tab
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: carson, Assigned: bugs)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041022 Firefox/1.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041022 Firefox/1.0 This is with AVIARY_1_0_20040515_BRANCH as of 2004-10-22 at 17:00 US/Eastern Either right click on a link and select "Open Link in New Tab" or middle-click on a link. A new tab is created, but it is a blank (Untitled) tab. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Comment 1•20 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041023 Firefox/1.0 WFM
Comment 2•20 years ago
|
||
if the link in question is a javascript link, that would be the problem. If so, this is a dupe.
Comment 3•20 years ago
|
||
Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1 This is entirely reproducible for me on Windows NT 4.0. *Every* link I ctrl-click on (not just Javascript links) opens an empty (Untitled) tab.
Comment 4•20 years ago
|
||
in fact, this bug is critical for me as it effectively means I can't use tabbed browsing and therefore can't use this version of the browser. It's back to the PR for me...
Comment 5•20 years ago
|
||
disable all extensions and try again , preferably with FF1.0RC1
Comment 6•20 years ago
|
||
(In reply to comment #5) > disable all extensions and try again , preferably with FF1.0RC1 Hi, I tried that already. I had tabbrowser extensions (by Shimoda Hiroshi), and suspecting that it might be incompatible with FF1.0RC1, I uninstalled it. That was the only extension I had, but the problem still happened after restarting FF. Andrew
Comment 7•20 years ago
|
||
TBE = Evil and should not be used with FF It causes loads of problems on all OS. Try a new install with newly installed profile , that should fix it
I have found this to be a problem on Win32 only. Appeared at some time between 2004-09-30 build (last I downloaded before my current version) and 2004-10-22 build. Has persisted through 1.0rc2 on Win32.
Comment 9•20 years ago
|
||
(In reply to comment #7) > TBE = Evil and should not be used with FF > It causes loads of problems on all OS. > Try a new install with newly installed profile , that should fix it I did as you suggested and opening links in new tabs works fine now with 1.0RC1. BTW - I have used TBE for a long time on several Windows OS's and never found it evil before (until now???) Thanks, Andrew
Comment 10•20 years ago
|
||
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 I can confirm this to be a problem with Slackware 9.1.0. The Firefox .9 version worked great, but when 1.0 came out this started occuring.
Comment 11•20 years ago
|
||
Another note: When configured to "open in new tab", links opened from Thunderbird also create an empty tab. If Firefox is not already open, the link opens correctly in a new browser window.
Comment 12•20 years ago
|
||
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20041127 Firefox/0.9.1+ This build seems fixed for this particular bug. Tabs open with their correct content.
Comment 13•20 years ago
|
||
(In reply to comment #10) > Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 > > I can confirm this to be a problem with Slackware 9.1.0. The Firefox .9 version > worked great, but when 1.0 came out this started occuring. > Same for me with Slackware 9.0. The 0.8 works fine.
Comment 14•20 years ago
|
||
This bug is the same on my machine running Linux Fedora Core.
Comment 15•20 years ago
|
||
Deleting the fiefox directory and reinstalling and wiping out the profile fixed the problem.
Comment 16•20 years ago
|
||
others, does a new profile fix this problem for you?
Comment 17•20 years ago
|
||
Resolving bug WFM. The active people in this bug have reported that the issue is gone.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•