Closed Bug 104566 Opened 23 years ago Closed 5 years ago

Ability to place tab bar in different positions on the window

Categories

(SeaMonkey :: Tabbed Browser, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1607041
Future

People

(Reporter: bhun2858, Assigned: jag+mozilla)

References

Details

It would be nice if the tab bar could placed at the bottom, left or right edges of the window.
related: bug 104324
Marking new
Status: UNCONFIRMED → NEW
Ever confirmed: true
i think bug 104324 covers the desired behaviour. Tabs on left/right side of browser would clutter sidebar/scrollbar.
*** Bug 105447 has been marked as a duplicate of this bug. ***
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0.1
spam: set your filter for "SeverusSnape" to avoid the influx of bugmail changing QA contact of open tabbed browser bugs from blake to me. if this bug requires a reassignment, however, feel free to change it!
QA Contact: blakeross → sairuh
like bug 105885, this would be swell...
Keywords: nsbeta1
Bottom seems like a possible default to me, leveraging user familiarity with tabs used for MDI windows, and sheet tabs for Excel. Of course, the similarity to these could be a disadvantage too, due to negative transfer of training.
OS: Windows 98 → All
Hardware: PC → All
Reassigning to new component owner.
Assignee: hyatt → jaggernaut
Status: ASSIGNED → NEW
-> future
Target Milestone: mozilla1.0.1 → Future
*** Bug 124194 has been marked as a duplicate of this bug. ***
*** Bug 125289 has been marked as a duplicate of this bug. ***
nsbeta1-
Keywords: nsbeta1nsbeta1-
*** Bug 135426 has been marked as a duplicate of this bug. ***
*** Bug 149915 has been marked as a duplicate of this bug. ***
*** Bug 157961 has been marked as a duplicate of this bug. ***
QA Contact: sairuh → pmac
Summary: [RFE] Ablity to place tab bar in different positions on the window → Ablity to place tab bar in different positions on the window
Keywords: nsbeta1-
Summary: Ablity to place tab bar in different positions on the window → Ability to place tab bar in different positions on the window
Some of this seems less likely now that those funny little arrow thingies at the left of the toolbars are gone (due to bug 112534)
Right, the grippies were originally used as a drag affordance for toolbars in Nav 4.x, which is how NS users would expect to be able to reposition tab bar too. We may still have to add them back to the NS product.
Isn't this really a dupe of bug 15322?
*** Bug 180801 has been marked as a duplicate of this bug. ***
> Isn't this really a dupe of bug 15322? No. The tab bar isn't a toolbar proper, nor does bug 15322 pertain to moving toolbars to other sides of the screen (left/right/bottom).
*** Bug 210636 has been marked as a duplicate of this bug. ***
adding myself to cc.
See also bug 218280, same bug for Firebird.
FWIW: From a recent MozillaZine discussion, here's a way of having tabs appear at the bottom of the screen. Edit your userChrome.css profile file, and add the following: #content > tabbox {-moz-box-direction: reverse;}
*** Bug 223013 has been marked as a duplicate of this bug. ***
I personally would need to put the tab bar at the left of the screen. In that position under Opera and Galeon I can mantain about 20 tabs opened without bar scrolling... Thanks a lot.
QA Contact: pmac → bugzilla
Product: Core → SeaMonkey
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Status: UNCONFIRMED → NEW
Ever confirmed: true

Sorry it took 19 years to solve. I didn't get around to it before.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.