= 1 does not open external links in the same tab




10 years ago
10 years ago


(Reporter: notify_craig, Unassigned)


Firefox Tracking Flags

(Not tracked)




10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/2009011913 Firefox/3.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/2009011913 Firefox/3.0.6

My understanding is that when I set = 1 all "external" links--ones I click on from programs outside of Firefox--should open in the same tab.  Instead, they still open in a new tab.

Reproducible: Always

Steps to Reproduce:
1. open Firefox
1a. make sure F.F is the default browser
2. go to about:config
3. filter by "window"
4. change value to 1
5. close browser (not sure what makes this value persistent)
6. open browser
7. in a separate application, click on a hyperlink

Actual Results:  
Hyperlink opens in a new F.F. tab.

Expected Results:  
Hyperlink should open in the same F.F. tab.

I have some add-ons installed:

Firebug 1.3.3
Java Quick Starter 1.0
Mouse Gestures 2.0.3

Build config:


Build platform

Build tools
Compiler 	Version 	Compiler flags
cl 	14.00.50727.762 	-GL -wd4624 -wd4952 -TC -nologo -W3 -Gy -Fd$(PDBFILE)
cl 	14.00.50727.762 	-GR- -GL -wd4624 -wd4952 -TP -nologo -Zc:wchar_t- -W3 -Gy -Fd$(PDBFILE)

Configure arguments
--enable-application=browser --enable-update-channel=release --enable-optimize --disable-debug --disable-tests --enable-update-packaging --enable-official-branding --enable-jemalloc --with-crashreporter-enable-percent=10

Comment 1

10 years ago
I played with just to see, but it didn't make any difference.

Also, I ran in safe mode (firefox.exe -safe-mode) and selected "Disable all Add-Ons" but that didn't help either.
Hmm, AFAIK, it's setting that will control external links and (and .restriction) is only for links clicked inside Firefox itself.

Comment 3

10 years ago does not work either in 3.5.
Yeah, I noticed. Luckily there's a handy add-on in bug 469082 that fixes this bug (by bringing back since it probably won't get fixed because core devs seems to be thinking that this is the right way to go. :(

Comment 5

10 years ago
Right way to go??  IMO, it should be going even more the other way: Browsers should be evolving to have more intelligence--and complementary user options--around tabs and when to create new ones.  For instance, I think it would be great to be able to turn on an option where a newly requested URL opens in the current tab if the current tab contains a page with the same TLD as the requested URL, and conversely, it opens in a new tab if its TLD is different.  Does anyone see a problem with browser starting to adopt this can of behaviour (as an option)?

Comment 6

10 years ago
This appears to be fixed in version 3.5 but I don't know the accepted protocol for updating the status.  Should I mark it Resolved?

Comment 7

10 years ago
Yeah, since we don't know which exact changeset changed the behavior fixed, it's RESOLVED/WORKSFORME.
Last Resolved: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.