should be able to have all sidebar tabs on the top

RESOLVED EXPIRED

Status

SeaMonkey
Sidebar
--
enhancement
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: bsaylor, Unassigned)

Tracking

({helpwanted})

Trunk
x86
Linux
helpwanted

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9+) Gecko/20020318
BuildID:    2002031822

It is cumbersome to have sidebar tabs both on the top and bottom of the sidebar,
because you sometimes have to look in two places and move the mouse a fair
distance to switch between tabs.  For example, I like to switch between
bookmarks and history, and to do that I need to click near the top of the
sidebar for bookmarks and near the bottom for history.  Also, since my search
tab is between bookmarks and history, it may be on the top or bottom depending
on which other tab is open.

At least, it would be nice to have an option to have all tabs always on the top
(or bottom) of the sidebar.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 1

16 years ago
helpwanted
Keywords: helpwanted
Target Milestone: --- → Future

Comment 2

15 years ago
For another idea to reduce the mouse travel times see Bug 209165.
Product: Browser → Seamonkey
Assignee: samir_bugzilla → nobody
QA Contact: sujay → sidebar
Target Milestone: Future → ---

Comment 3

9 years ago
MASS-CHANGE:
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

Comment 4

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.