Open
Bug 515410
Opened 16 years ago
Updated 10 months ago
Allow links from external applications to not replace open tabs, when Firefox is set to block target=_blank pop-ups
Categories
(Firefox :: Settings UI, enhancement)
Firefox
Settings UI
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| blocking2.0 | --- | - |
People
(Reporter: bugzilla, Unassigned)
Details
(Keywords: dataloss, ue)
Attachments
(1 obsolete file)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; da; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; da; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729)
(From Mike Beltzner's suggestion in bug 469082 comment 19)
I would like Firefox to not override/replace an open website/tab when handling a link from an external application, even when Firefox is set to not allow pop-ups created by web sites with <a target="_blank">.
The current values for browser.link.open_newwindow are:
1 = current window/tab
2 = new window
3 = new tab in most recent window
I would like to add a new value:
4 = current window/tab, except if the link comes from an external application, then use a new tab in most recent window instead
If possible, i have seen the following values requested by others, so I would also like to add those:
5 = current window/tab, except if the link comes from an external application, then use a new window instead
6 = new tab in most recent window, except if the link comes from an external application, then use a new window instead
If that is not possible, I would like to just add the new value of 4.
I would like to stress that I do NOT want to revert bug 324164. That bug was a good change overall. Only some of the side effects of the bug removed functionality wanted by me and obviously many others.
For the history of this, see bug 469082, bug 324164 and MozillaZine threads.
If this is accepted, I am willing to write the patch.
Reproducible: Always
Steps to Reproduce:
1. Set browser.link.open_newwindow to 1 in about:config, so that Firefox does not open popups on links with target=_blank, such that the back button always works correctly.
2. Open a link from an e-mail or another extarnal application.
Actual Results:
The current tab is replaced with the new link, and any information on that page may or may not be lost.
Expected Results:
The link opens in a new tab or window. Leaving all of your currently open web sites intact.
(Please anybody avoid destructive "me too" comments and complaints)
Comment 1•16 years ago
|
||
Why not just add a new preference to suppress target="_blank" behaviour? It achieves all of the above (except the destructive no. 1 and the likely-lost-forver no. 6) and maintains the simplicity and consistency that is apparently the reason these preferences were unified in the first place.
| Reporter | ||
Comment 2•16 years ago
|
||
(In reply to comment #1)
> Why not just add a new preference to suppress target="_blank" behaviour? It
> achieves all of the above (except the destructive no. 1 and the
> likely-lost-forver no. 6) and maintains the simplicity and consistency that is
> apparently the reason these preferences were unified in the first place.
Because Mike suggested that the the solution in comment 0 actually might be accepted, which is better than nothing.
Comment 3•16 years ago
|
||
The "likely-lost-forver no. 6" is exactly the behaviour I prefer, which demonstrates why simply adding a couple more values for what is truly a two-dimensional (at least 3x3) choice is a relatively poor option.
100% behind this. I don't want new tabs to open because people used _blank on all links without thinking about usability or wanted their page to stay open for ad serving purposes and I use a desktop feed reader and open a lot of external links. Overwriting the same tab again and again...I know there is tabmixplus but this IMO should be in the browser like it was in 3.0.x series.
Comment 5•16 years ago
|
||
(In reply to comment #3)
> The "likely-lost-forver no. 6" is exactly the behaviour I prefer, which
> demonstrates why simply adding a couple more values for what is truly a
> two-dimensional (at least 3x3) choice is a relatively poor option.
Well, yeah, having made the original change at all was silly from the perspective of user experience. And putting it back the way it used to be would make the most sense, because it offered the most flexibility without sacrificing simplicity.
So ultimately I do agree with you; but at any rate I'd just like them to do *something* before they stop updating 3.0.x. Otherwise I'll have to switch browsers or find and thoroughly test an extension; I'd rather not have to go to all that trouble.
(If there's a good Firebug replacement out there that works with Safari, of course, I'd love to know about it. If you know of a viable replacement, please contact me by e-mail!)
| Reporter | ||
Comment 6•16 years ago
|
||
Comment 7•16 years ago
|
||
Confirming, this is a valid enhancement request (although this may end up as wontfix).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: unspecified → Trunk
Comment 8•15 years ago
|
||
If external links opens in new tab instead in current tab when target _blank is prevented would be very nice.
Comment 9•15 years ago
|
||
In bug 469082 comment 19 by Mike Beltzner:
> If you want to create a value of 4 that acts differently for external
> applications, I'd consider that patch, but that's a different bug than this
> one, which is claiming that we're behaving incorrectly.
blocking2.0: --- → ?
Updated•15 years ago
|
Comment 10•15 years ago
|
||
Just to point out the absurdity of the developers' resistance to restoring the separate built-in option for browser.link.open_external, I've now found myself making use of an extension called "Tabs Open Relative (Modified)" not because I want the behavior named by the extension - I happen to detest it - but because, now that the named behavior has been added as built-in option browser.tabs.insertRelatedAfterCurrent, the extension's only actual function is to restore the open_external option!
Comment 11•15 years ago
|
||
Not blocking, but would happily approve a patch for Firefox 4.
blocking2.0: ? → -
Updated•3 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Attachment #9386387 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•