Open Bug 156916 Opened 23 years ago Updated 4 years ago

Make Open A new tab/window button available (when the tab bar is closed/ or always)

Categories

(SeaMonkey :: Tabbed Browser, enhancement)

x86
All
enhancement
Not set
normal

Tracking

(Not tracked)

People

(Reporter: aryanameri, Unassigned)

References

(Blocks 1 open bug)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1a+) Gecko/20020708 BuildID: 2002070821 In newer Builds ( 2002070821), A button has been added to the left of the Tab Bar called "Open a New tab". This is actually a very nice feature , since it enables you to quickly open new tabs with a single click. How ever as this button resides in the tab bar,and as by default, the tab bar is hidden when you only have one open tab, therefore, This button is not always available. As a matter of fact it is not vailable usually, when you first open mozilla. As this feature really makes opninning new tabs very easy, and as tabbing has become so much popular recently, therefore I would like to see this "Open a New Tab" button" available, even if the tab bar is closed. Reproducible: Always Steps to Reproduce: 1.Open Mozilla, and by default, as tab bar is hidden, you won't see the "Open A New Tab" Button.
If you like tabs so much you should disable the preference to hide the tab bar when only 1 tab is present.
-> UI design
Assignee: jaggernaut → mpt
Component: Tabbed Browser → User Interface Design
QA Contact: sairuh → zach
please wontfix. if people want to use tabs, they should opt in to always seeing the tabbar and be happy. if a person does not want to use tabs, we should *not* spend their valuable real-estate on a button which they will not use.
Whiteboard: DONTFIX
this bug is similar to 104125
I don't think it's at all similar to 104125. This bug is talking about Tabed browsing, while 104125 was made at a time when tabbed browsing didn't existed ( Or was in it's early stages perhaps). The bug 104125 wants a button to do the job of Ctrl+N. I want a Button with the outcome of Ctrl+T. Are they similar? BTW: I agree that we timeless@mac.com that we shouldn't waste valuable real-estate. But IMHO making it an optional button ( perhaps like the Go and Print and Search Buttons), won't force users into anything. Aryan
No offense to him, but why is mpt the assignee when we all know how much he hates tabbed browsing?
Well, I don't know much about the history of mozilla or the people there.( I'm trying to learn it), but can you refer me to a bug or something that shows mpt hates tabbed browsing? As this bug have not received any attention maybe I should change the assignee. BTW: I know that Gecko is by far the superior engine or that mozilla is much more standard oriented than IE, but I can't tell these to the average user, when I am encouraging them to switch from IE to mozilla. What I am able to tell them is that it has tabbed browsing, or it blocks, pop up ads an etc. That's what most people really care about. Therefore, I think we should make mozilla, even stronger in fields that it has advantages over IE. Tabbed browsing is one of them, that IE lacks, so we should work on it more.Also, I had a case when the user hated Mozilla, but when I changed the theme, he started loving it. GUI is what most people see. Aryan
OS: Linux → All
Whiteboard: DONTFIX
See also bug 104125, "one-click button for new browser window".
Status: UNCONFIRMED → NEW
Depends on: 15144
Ever confirmed: true
->Tabbed Browsing component
Assignee: mpt → jaggernaut
Component: User Interface Design → Tabbed Browser
QA Contact: zach → sairuh
Well, bug 104125 is similar to bug 156916 . But they are not duplicates, About 15144 , I agree that it is a great enhancement, that many ( including me ) would love it, and if bug 15144 is fixed, both bug 104125 and this bug won't need any further attention. But still I don't think this bug depends on 15144 because it can be implemented, even without bug 15144 being fixed.
No longer depends on: 15144
Depends on: 15144
WONTFIX please! If you want to use tabs, then turn on "always show tabs". Perhaps that should even be the default now, since it's so popular. One thought: if Netscape gets (user) customisable toolbars, as it probably should, then those people who want this could add a "new tab" button to one of their toolbars.
I agree, tab bar should be on by default for easier discovery, and if the user closes it they probably don't want the new tab button either. In any case, customization takes care of the edge case.
OK, I also Agrre. This bug will now be resolved as WONTFIX. Since people complaint about having such a button, and besides, if we can really have customized toolbars, that will take care of this bug. As we have had a bug for such a task (Which I mentioned before), thus there is no need for this bug.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
v
Status: RESOLVED → VERIFIED
closed now
Status: VERIFIED → CLOSED
*** Bug 172069 has been marked as a duplicate of this bug. ***
*** Bug 197851 has been marked as a duplicate of this bug. ***
Product: Core → SeaMonkey
No longer depends on: 15144
(In reply to comment #13) > OK, I also Agrre. This bug will now be resolved as WONTFIX. Since people > complaint about having such a button, and besides, if we can really have > customized toolbars, that will take care of this bug. As we have had a bug for > such a task (Which I mentioned before), thus there is no need for this bug. now we have customizable toolbars, but not "new tab" and "new window" buttons. On Fx "new tab" is my first button and the most used one. I have customized same way for many of my friends and they love it. Yesterday I switched from back Fx(phoenix/Fb) to SM. I was delaying this because SM did not have customizable toolbars earlier.
Status: CLOSED → REOPENED
Resolution: WONTFIX → ---
Summary: Make Open A new tab button available when the tab bar is closed → Make Open A new tab/window button available (when the tab bar is closed/ or always)
Blocks: 157199
Assignee: jag → nobody
Status: REOPENED → NEW
QA Contact: bugzilla → tabbed-browser
You need to log in before you can comment on or make changes to this bug.