Closed
Bug 436760
Opened 16 years ago
Closed 16 years ago
Firefox does not respect GNOME's antialiasing prefences
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 404637
People
(Reporter: thomas, Unassigned)
Details
Attachments
(1 file)
26.57 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9) Gecko/2008051202 Firefox/3.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9) Gecko/2008051202 Firefox/3.0 In GNOME on Ubuntu 8.04 Hardy Heron I currently have my antialiasing settings set for subpixel smoothing, to make it less sharp on the eyes. However, Firefox 3.0 does not seem to respect the settings, and the text appears sharper than it should. (See screenshot) Reproducible: Always Steps to Reproduce: 1. In Ubuntu Linux, set antialiasing to sub-pixel smoothing (on LCDs only, otherwise it looks ugly) 2. Open a Firefox window, compare Ubuntu menu bar and Firefox menu bar, you can see it's definately much sharper. Actual Results: Firefox appeared much sharper than the system overall. Expected Results: It should query GNOME and act appropriately. Ubuntu 8.04 Hardy Heron. Firefox 3.0 Release Candidate 1. I currently have Firefox 3.0 beta 5 installed, I am just running this to test it, I have not replaced it or updated any profile, if that matters.
Reporter | ||
Comment 1•16 years ago
|
||
Screenshot of problem in Ubuntu Linux with subpixel smoothing enabled.
Reporter | ||
Updated•16 years ago
|
Attachment #323274 -
Attachment description: screenshot of problem, cropped down a bit. → screenshot of problem, cropped down a bit
Comment 2•16 years ago
|
||
the opposite problem is mentioned in bug 433659, with a number of tips.
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Comment 4•16 years ago
|
||
The issue is with Cairo. Firefox uses its own version of Cairo that is different from the one used by GNOME. If you if you use the Firefox 3 version from Ubuntu you shouldn't see this issue.
You need to log in
before you can comment on or make changes to this bug.
Description
•