Problem: Both the Modern and Classic skins now display the menus with the default 'display font' as specified in viewing web pages. This should be considered a regression unless this issue was intentional. Steps to Reproduce or Demonstrate: Change the font preferences to use serif, or sans-serif for displaying messages and Mozillas skin will change to use that preference in its menus upon new window creation or upon closing and opening of Mozilla. This changed between 2002022109 and 2002022203 win32-nightly builds. If I have 'Comic Sans' defined as my font for menus under 'Windows Appearance' preferences in Windows 2000, then Mozilla needs to use those (it used to.) Recommendation: This needs to be either a separate preference under fonts (Mozilla Appearance) with use System or theme font as an option plus the list of available fonts or Mozilla needs to use the fonts specified by the system (previous behavior.) Notes: In some situtations you might to use Sans Serif fonts [e.g. windows default menus] for menus, control boxes, dialog boxes, UI, etc. and Serif fonts for the default display font for webpages and email so you can verify HTML tables and stylesheets for proper font settings. [Default Netscape 4.x behavior] I'm not sure if Preferences is the correct place for this. Someone please reassign to the appropriate component if otherwise...
WORKSFORME with build 2002022203, Win98.
Assignee: sgehani → hewitt
Component: Preferences → Themes
QA Contact: sairuh → pmac
wfm, win98SE, 2002022203, BUT: it only kicks in on new windows. Existing windows stick with what they've got, unlike other windows apps, which pick up the change immediately. Reporter, can you clarify what you're seeing a bit?
This was user error: The windows font cache went kah-plooey and that's why I lost the system fonts. (They didn't exist to the system...) Apparently, if the 'system' font is unavailable, Mozilla hunts for a font mentioned in the prefs rather than system specified... Can we mark this as reporter stupidity? :-)
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.