The menu of the site appears disfigured



15 years ago
13 years ago


(Reporter: Alexandre Gomes, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)





15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040120
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040120

Go to, you will see that the menu have a vertical separators
that doesn't appear well. The lines are too up. Compare with IE

Reproducible: Always

Steps to Reproduce:

Comment 1

15 years ago
Mozilla 1.7a
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040120

The OP's actions were taken to check the bug
And the bug *exists*.

Actual result: The vertical lines in the top menu are extened beyond the menu
Expected result: The vertical lines should be restricted to the menu.

Looking at the HTML source, the <span class="SeparatorTabsBg"> seems to be the
one which might be the reason for the problem

So ths site expects |0.7*font_size + 2px == font_size| to hold -- the vertical
lines are made by spans with a "normal" font size (whatever the inherited size
is), while the horizontal lines are the top/bottom borders on 0.7*font_size text.

Note that the identity is only satisfied if the text is 7px tall or so.

Also note that IE's handling of borders on inlines is very buggy, so it looks
like this site is just working around IE bugs and screwing over any browser that
handles inline borders decently in the process...

Comment 3

15 years ago
yep confirming this one on:

ozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040303
Firefox/0.8.0+ (mmoy)
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.