279726 - Single window mode option

Status: RESOLVED INVALID

(Firefox :: Tabbed Browser, enhancement)

Description

[Stasys Adiklis]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I'd like to be able to shift+click into a new Tab just like i do that in Crazy
Browser (IE shell).

An idea to train me into switching between shift+clicking and ctrl+clicking as i
switch between Crazy Browser and Firefox is not welcome, to put it lightly.

Tabbrowser Extensions can do that but last time i checked they were evil.


Reproducible: Always

Steps to Reproduce:

Comment 1

[Matthias Versen [:Matti]]

shift+click is save as and I can't see a reason to change that.
Use a extension if you need this...

Comment 2

[Stasys Adiklis]

"shift+click is save as"

Wrong. It's 'open in new window' (on W2000).

"Use a extension"

Wrong again. Read this:
http://piro.sakura.ne.jp/xul/tabextensions/tradeoff.html.en#opinion-of-firefox-developers

"I can't see a reason to change that"

Fine with me. That's why i'am asking for an OPTION.

Reopening.

Comment 3

[mmortal03]

I'm confused.  We already have a single window mode.  It is just, at the moment,
hidden from the advanced options because of some small bugs going into 1.0.  To
access it, add browser.tabs.showSingleWindowModePrefs to about:config (if it
isn't already there) and set it to true.

As for clicking into a new tab, you can middle click any link (sans Javascript)
to do this.

Comment 4

[:Gavin Sharp [email: [e-mail]]]

Changing Firefox to conform with CrazyBrowser so that you can feel comfortable
is not something that will be done. As [e-mail] said, there already
are Single Window mode options.

Comment 5

[Stasys Adiklis]

"Changing Firefox to conform with CrazyBrowser so that you can feel comfortable
is not something that will be done."

Well, the two browsers that i'm using (Tabbrowser Extensions and Crazy Browser)
offer this. Don't care about CB? Fine. Let's talk about TE only.

Tabbrowser Extensions are "strongly unrecommended" and Mozzillerz have asked to
submit info on wanted features that TE has but Firefox does not. I've already
dropped a link where you can find that very request.

Anyway, what's important is that the suggested
browser.tabs.showSingleWindowModePrefs option does not work. Iv'e submitted a
new bug report on this: bug 279864.

Comment 6

[Stasys Adiklis]

Gavin, listen carefully.

Your interpretation of my intentions in your response to bug 279864: "that's
because you're explicitly telling it (with shift) to open a new window" is
wrong. I'm shift+clicking a link with an intention to kick it out of it's
present frame (i don't know if this term is perfectly ok but that's besides the
point) as opposed to asking it to reuse it (just click). Where will that link
go? It can go to a new Window (as is the case with IE and MF) or, it can go to a
new tab (as is the case with CB and TE (when its "Single Window Mode" is on)).

I don't think that "single window mode" should not exclude multiple windows. If
you do - OK. Just add an extra sub-option called "all links!" to the "Force
links that open in new windows to open in: a new tab" option.

Maybe you misinterpreded my "as i switch between Crazy Browser and Firefox"? I
don't mean here migration from CB to MF. I don't have plans to stop using IE
(CB) on Windows entirely any time soon. The switching i'm talking about is
Alt+Tab kind of switching. I don't want to do some sort of context switching in
my brain everytime i switch between those two browsers. A single checkbox option
can solve the problem just fine. That's what i'm asking for.

"That feature is going to be revisited in upcoming releases anyways." Good.
That's why my RFE is timely. It would be bad not to give you a chance to
consider users' needs as you're "revisiting".

Comment 7

[Stasys Adiklis]

BTW there is another good reason to make Single Window Mode truly Single Window
Mode. It would give a chance to implement Persistent Tab Session mode in a
simple way as i've suggested in comment 41 for bug 159357.

Comment 8

[Stasys Adiklis]

I'm closing this as invalid because bug 279864 formulation makes more sense.