183882 - [classic:] wrong (bold) menu font when anti-aliasing is enabled

Status: RESOLVED EXPIRED

(Core :: XUL, defect)

Description

[Stefan A. Möller]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130

When you enable anti-aliasing (FreeType2) in unix.js, the menu fonts of the
first Mozilla window opened appear bold (and seem to be anti-aliased). All
subsequently opened windows have normal menu fonts again.
This bold font is bad especially in mail/news where you cannot distinguish bold
and non-bold text any more.

Reproducible: Always

Steps to Reproduce:
1. Enable anti-aliased TT fonts as described in
http://mozilla.org/projects/fonts/unix/enabling_truetype.html
2. Switch to classic theme
3. Close Mozilla, then open two new Mozilla windows


Actual Results:  
Different menu fonts in those 2 windows.

Expected Results:  
Menu fonts should be the same (non-bold and non-AA I think, like in the other
Gtk applications).


My font setting in .gtkrc is
  fontset = "-microsoft-Verdana-medium-r-normal--*-110-*-*-p-*-iso8859-15"

Comment 1

[Stefan A. Möller]

Attachment: screenshot

Comment 2

[Stefan A. Möller]

I've chosen the wrong component for this bug. The problem is not theme specific,
it's just more visible in classic. With modern theme the "go" and "search"
buttons and the sidebar heading show the same effect.

Comment 3

[Gervase Markham [:gerv]]

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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

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.