After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 333801 - Font family preference for Serif is broken
Font family preference for Serif is broken
Status: RESOLVED DUPLICATE of bug 324717
Product: galeon
Classification: Deprecated
Component: Mozilla interaction
2.0
Other All
: Normal normal
: ---
Assigned To: galeon-maint
galeon-maint
Depends on: 324717
Blocks:
 
 
Reported: 2006-03-07 21:41 UTC by Tobia Conforto
Modified: 2006-03-19 21:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tobia Conforto 2006-03-07 21:41:58 UTC
Please describe the problem:
The user preference on which font to use as serif is completely ignored.
The standard system font called "Serif" is used instead.

Steps to reproduce:
1. Edit, Preferences, Fonts, choose your default encoding, and under Serif
choose a weird font
2. Paste the following into the address bar:
data:text/html,<span style="font-family:serif">Test

Actual results:
The word Test is displayed with some system-wide Serif font

Expected results:
The word Test should be displayed with the chosen weird font

Does this happen every time?
Yes

Other information:
This is NOT http://bugzilla.gnome.org/show_bug.cgi?id=324717

This only seems to happen to serif and possibly monospace. Sans-serif, cursive,
and fantasy are ok.

This bug, coupled with the aforementioned 324717, means that most web pages are
displayed with the system-wide "serif" font, which on some systems is ugly.

This is actually Galeon 2.0.1 on Debian Sid, but the nearest version number in
Bugzilla in 2.0. Galeon 2.0 didn't have this bug.
Comment 1 Loïc Minier 2006-03-19 21:26:39 UTC
Hmm, I fail to see how this differs from bug 324717.  For me, bug 324717 is summarized in the fact that galeon used a global serif/sans serif switch, and now needs a per-encoding/language serif/sans-serif switch (via the font.name.variable.$encoding prefs).

If I set font.name.variable.x-western to serif in my prefs.js, your sample content is displayed with the configured serif font (font.name.serif.x-western).
Comment 2 Crispin Flowerday (not receiving bugmail) 2006-03-19 21:40:21 UTC
Yes, this is almost certainly related

*** This bug has been marked as a duplicate of 324717 ***