Closed Bug 468973 Opened 16 years ago Closed 15 years ago

3.1b2 doesn't honor browser.link.open_external = 2 (Open in New Window)

Categories

(Firefox :: General, defect)

defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: erik, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2

While 3.1b1 removed the preferences UI for browser.link.open_external, it honored the setting if entered via about:config. 3.1b2 ignores the setting and uses the default (3, "Open in a new tab in the current window"). I have not tried setting the value to 1 ("Open in current window") to see if that's honored.

Reproducible: Always

Steps to Reproduce:
1. Set Firefox as your default browser 
2. set browser.link.open_external = 2 in about:config
3. open URL externally. Any program should work (as should "open '<url>'" on the command line)
Actual Results:  
New URL opens in a tab in the current window

Expected Results:  
New URL opens in a new window

I can't believe this isn't a duplicate bug, but I've searched quite a bit and can't find a previous submission.
Also happens on Windows, so -> All.

I still don't know whether this is a bug, though.  Or how the
following settings are supposed to behave (and whether they may
override browser.link.open_external):

browser.link.open_newwindow
browser.link.open_newwindow.restriction
OS: Mac OS X → All
Hardware: PC → All
browser.link.open_newwindow & browser.link.open_newwindow.restriction detail how to behave when a link or javascript try to open a new window (via target="_blank" or JS popup)

While they're related, the behavior is currently separate (though 3.1b2 is not honoring that)

http://kb.mozillazine.org/Browser.link.open_newwindow
http://kb.mozillazine.org/Browser.link.open_newwindow.restriction
Flags: blocking-firefox3.1?
the behaviour is no longer separate, as of bug 324164

The prefs have been collated in the UI since around Firefox 2, IIRC, this was just a housecleaning op.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Flags: blocking-firefox3.1?
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.