Closed Bug 173406 Opened 22 years ago Closed 22 years ago

"Open in tabs" should have a prefable option: replace vs. append

Categories

(Firefox :: Bookmarks & History, defect)

Product:
Firefox
Component:
Bookmarks & History
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED FIXED
Milestone:
Phoenix0.3

People

(Reporter: hyatt, Assigned: p_ch)

References

Details

Open in tabs should do either a replace (blowing away existing tabs) or an append (creating a new set of tabs) based off a preference in the Tabbed Browsing panel. The default for this pref should be "replace" IMO.
Should fix for 0.3.
Target Milestone: --- → Phoenix0.3
fixed
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
REOPENED Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030714 Mozilla Firebird/0.6 I do not see the mentioned preference anywhere.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
*** Bug 174332 has been marked as a duplicate of this bug. ***
*** Bug 175335 has been marked as a duplicate of this bug. ***
This is no longer a visible pref since around February, but the pref does exist. If its going to be added back in, there is a bug already to restore UI for some of these tab prefs.
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → FIXED
taking QA contact, sorry about the bugspam
QA Contact: asa → mconnor
Is there a way this can be set via about:config until the UI option is re-added?
I doubt UI will be re-added at this point. browser.tabs.loadFolderAndReplace set to false does append
Status: RESOLVED → VERIFIED
"Normal" Mozilla (I think it's called "Seamonkey") seems to have such a feature, according to bug 222769. So why not adding this to Firefox!?
because the presence of UI for something is measured in "why" instead of "why not" seamonkey has about ten times as many visible prefs, most of which can still be set by users, but we removed many of them to reduce complexity. There's still debate on this elsewhere, resurrecting bugs that haven't had comments in a year is pointless.
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → bookmarks
As the "replace" option is destructive (and there's no way to undo), "append" should be the default unless and perhaps even if a UI option is added. More specifically, there's an easy workaround for creating the "replace" behavior (choose "Close Other Tabs" from the tab context menu), but there's no easy workaround for replacing tabs, at least not until tabs are easily movable between windows. This is a preference that probably doesn't deserve a UI option, but "safe" behavior should be preferred if the user has to understand about:config to change it.
There is no option in Firefox 3 to change from append to replace. The browser.tabs.loadFolderAndReplace option does not seem to work at all. I don't mind going to about:config for this, as long as it works, but it doesn't.
There is a big discussion and argument going on resulting in making browser.tabs.loadFolderAndReplace obsoleted !!! I do not want to go to the core of the argument "should open in tabs" overwrite existing open tabs or append. Both sides are valid and legitimate uses. Make one option a default - that would make supporters of one argument happy. Keep browser.tabs.loadFolderAndReplace working so supporters of another argument can be happy too. This may be silly but a lot of people are very unhappy with your arbitrary decision to go one way and lock out everybody else who do not agree with your choice. I am one of them and this alone may make me to stop using FF. I cannot believe what I am writing here but in 2008 a community driven project behaves like Stalin in 1938. Get a grip, please.
I agree. Everyday I visit lots of sites, and I open them in blocks based on folder of bookmarks. I find it correct and comfortable for the "Open all in tabs" command to overwrite existing tabs, so that when I change the bookmark block, the tabs I already opened disappear.
I agree with sawickig's comment; I happen to be on the disgruntled side of the recent Pidgin textbox-resize spat. A key to remember about Firefox is that we have the excellent option of leaving the internal config option in place and removing it from the default preferences UI; users who want to change the default can either use about:config or a simple extension. To Quintum, while you find a destructive "open all in tabs" to be useful, your use case has the option of opening a new blank window or using "close other tabs". With the current implementation of the tab system, the destructive "open all" is (1) surprising to at least some users, (2) not undoable, and (3) easy to hit by mistake. Generally speaking, it's desirable to have *any* destructive change undoable, and an operation that is both easy to invoke by accident and impossible to undo should not be the default.
I too agree with sawickig's comment. I routinely open groups of tabs while already having multiple tabs open THAT I WANT TO KEEP OPEN. Firefox has always been about being "customizable". Removing a very important user choice seems draconian. It is a sad day when Microsoft Internet Explorer starts to seem more customizable than Firefox. How soon can this very valuable asset be restored? A lot of us who migrated from Firefox 2.0.0.14 to 3.0 are SORRY we migrated. Please fix.
I'd really, really like to maintain the option. Like the earlier comments read: Firefox is about being customizable.
Is this "bug" by any chance a duplicate of: https://bugzilla.mozilla.org/show_bug.cgi?id=395024 (which deals with the about:cinfig entry "browser.tabs.loadFolderAndReplace")?
You need to log in before you can comment on or make changes to this bug.