153900 - [RFE] Excess Whitespace in Main Menu Bar Stealing Space from Content Pane

Status: RESOLVED EXPIRED

(SeaMonkey :: Themes, enhancement)

Description

[Felix Miata]

The font in the main menu bar is the same used in Netscape 4. Yet, the vertical
space consumed by this same component is about 25% larger in Mozilla,
unnecessarily vertical space better utilized by the main browser view pane. The
main menu bar should be the same height as used in Netscape 4.

This bug blocks bug 135457.

Comment 1

[Jo Hermans]

Why did you set this at "OS: All" ? I don't see this behaviour on either my Mac
OS 9, Mac OS X, Linux and Windows NT workstations. And I don't really see the
need to make it smaller, although the chrome could still be a bit improved : the
tabs could be a few fixels smaller for instance.

If you don't agree with the GUI, you can always use a different theme (or create
your own). The Pinball theme for instance, is nice, and quite a bit smaller than
Modern or Classic.

Comment 2

[Felix Miata]

A reading of blocked bug 135457 should be sufficient, but since you asked:

1-The owner of the specific platform for which bug 135457 was filed changed that
bug to ALL ALL.
2-The assignee of bug 135457 marked that bug invalid as a request to solve
multiple problems
3-I see the behavior described on Mandrake Linux 8.2 & Mozilla 1.0 at 800 X 600
4-I see the behavior described on W2K and Mozilla 1.0 at 800 X 600
5-I see the behavior described on OS/2 and all builds of Mozilla at 800 X 600

In case you are wondering where the 25% came from, it is 9/7 rounded down to the
nearest multiple of 5. I measured the height of the main menu bar in 4.x at 7 mm
and in Mozilla at 9 mm, both on same boot at 800 X 600.

If this behavior does not apply to Mac, then someone who can verify should
change OS to PC.

Comment 3

[Felix Miata]

original: s/unnecessarily vertical space/unnecessarily consuming vertical space/
comment 2: s/change OS to PC/change Platform to PC/

Comment 4

[timeless]

uid is being phased out.

Comment 5

[Robert Kaiser]

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

Comment 6

[Robert Kaiser]

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