Closed Bug 153902 Opened 22 years ago Closed 14 years ago

[RFE] Excessive Vertical Space in Off Toolbars (On Buttons) Stealing Space from Content Pane

Categories

(SeaMonkey :: Themes, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: mrmazda, Unassigned)

References

Details

Turning off the personal toolbar leaves wasted space the full width of the
browser approximately equal in height to one half the personal toolbar height,
leaving minimal point in turning it off, and no way to dispense with its
vertical waste entirely. The other toolbars, though taller when on, still leave
on buttons that consume too much vertical space. The on buttons for the toolbars
could be every bit as functional by sizing their height equivalent to the pane
switching buttons in mailnews. When only one toolbar is switched off, the on
button should be at one end of one of the other toolbars turned on or in the
tilebar instead of consuming exclusive space-wasting vertical space.

This bug blocks bug 135457.
Blocks: 135457
Status: UNCONFIRMED → NEW
Ever confirmed: true
uid is being phased out.
Assignee: mpt → shliang
Component: User Interface Design → Themes
QA Contact: zach → pmac
Product: Core → SeaMonkey
Assignee: shliang → nobody
QA Contact: pmac → themes
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
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
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.