Closed
Bug 320738
Opened 19 years ago
Closed 13 years ago
Firefox no longer renders fonts according to fontconfig setup.
Categories
(Core Graveyard :: GFX: Gtk, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 443308
People
(Reporter: futhark77, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051202 Fedora/1.5-0.fc4 Firefox/1.5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051202 Fedora/1.5-0.fc4 Firefox/1.5 I have tweaked my fontconfig setup so that only fonts of a given size get antialiased. That provides Firefox on Linux a font rendering that's pretty much the same I am getting on a Windows system. To my surprise, font rendering changed completely when I upgraded to 1.5. Firefox does not respect rules I defined in my ~/.font.conf. Since Firefox uses gtk and has a taste of Gnome, it didn't take long before I realize Firefox font rendering is controlled by gnome-font-properties program. I have yet to understand why though, as this program only provides a subset of the functionality I am getting with fontconfig. In short, the decision to link Firefox to gnome-font-properties is quite questionable. This bug may be the same as 307711. Reproducible: Always
Updated•19 years ago
|
Component: General → OS Integration
QA Contact: general → os.integration
Version: unspecified → 1.5 Branch
Updated•19 years ago
|
Component: OS Integration → GFX: Gtk
Product: Firefox → Core
QA Contact: os.integration → gtk
Version: 1.5 Branch → 1.8 Branch
Comment 1•19 years ago
|
||
Dupe of 243227. Been a problem ever since bug 197037 got fixed.
Comment 2•17 years ago
|
||
Does this bug occur in a recent trunk build? http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
Assignee | ||
Updated•16 years ago
|
Product: Core → Core Graveyard
Comment 3•15 years ago
|
||
this a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=443308
Comment 4•13 years ago
|
||
I concur.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•