Closed
Bug 660448
Opened 14 years ago
Closed 14 years ago
Subpixel antialiasing too strong/incorrect everywhere
Categories
(Core :: Graphics, defect)
Tracking
()
VERIFIED
FIXED
mozilla7
People
(Reporter: echogene.alpha, Assigned: joe)
References
Details
Attachments
(4 files, 1 obsolete file)
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0a1) Gecko/20110526 Firefox/7.0a1
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:7.0a1) Gecko/20110526 Firefox/7.0a1
Subpixel antialiasing has become too strong/wrong in the latest builds of Nightly. That is, where it is red and blue, it is too red and too blue. This happens on both web pages and the entire user interface (menu bar and below).
Reproducible: Always
Steps to Reproduce:
1. Open Firefox
2. Look at text
Actual Results:
Text looks weird. Upon zooming in, it's easy to see that subpixel antialiasing is wrong.
Expected Results:
Text should look like it did in previous builds.
Reporter | ||
Comment 1•14 years ago
|
||
A comparison of subpixel antialiasing in Nightly and Firefox 4.
Comment 2•14 years ago
|
||
That's a pretty glaring difference. Jeff, might this possibly be related to the recent cairo update (bug 562746)?
Updated•14 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•14 years ago
|
Component: General → Graphics
Product: Firefox → Core
QA Contact: general → thebes
Comment 3•14 years ago
|
||
The cairo update alone is definitely responsible for a change in text rendering on my Linux machine.
Updated•14 years ago
|
tracking-firefox7:
--- → ?
Comment 4•14 years ago
|
||
Since cairo 1.9.10, this change is in effect http://cgit.freedesktop.org/cairo/commit/?id=7a023a62f7517ad0d54f4d59c99909fadcc05e82
I think it maybe related, https://bugs.freedesktop.org/show_bug.cgi?id=34886#c3
(disclaimer: I am not an expert in cairo, freetype, fontconfig or mozilla; so don't take what I say to heart... :)).
Assignee | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 6•14 years ago
|
||
OK, I'm going to undupe this for a short-term patch. The long-term fix is bug 456448, but we're blocked on releng for that.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Assignee | ||
Comment 7•14 years ago
|
||
OK, let's just dlsym() FT_Library_SetLcdFilter for now. This is not a long-term fix, because on computers that don't have this symbol we'll be a rainbowy mess. (We have to stop supporting distributions with old freetypes.) But until all the infrastructural work to upgrade Freetype and stop supporting old versions of it is done, this'll do.
Assignee: nobody → joe
Status: REOPENED → NEW
Attachment #538345 -
Flags: review?(karlt)
Attachment #538345 -
Flags: review?(bjacob)
Assignee | ||
Comment 8•14 years ago
|
||
Forgot to qrefresh.
Attachment #538345 -
Attachment is obsolete: true
Attachment #538345 -
Flags: review?(karlt)
Attachment #538345 -
Flags: review?(bjacob)
Attachment #538346 -
Flags: review?(karlt)
Attachment #538346 -
Flags: review?(bjacob)
Updated•14 years ago
|
Attachment #538346 -
Flags: review?(bjacob) → review+
Comment 9•14 years ago
|
||
Comment on attachment 538346 [details] [diff] [review]
dlsym FT_Library_SetLcdFilter for now
I probably would have replaced initialized_setLcdFilter with
static setLcdFilterFunc setLcdFilter =
(setLcdFilterFunc) dlsym (RTLD_DEFAULT, "FT_Library_SetLcdFilter");
in the code block scope but I haven't checked the C standard to make sure that is called on first pass, and what you have does the right thing.
Attachment #538346 -
Flags: review?(karlt) → review+
Assignee | ||
Comment 10•14 years ago
|
||
That's how I started out, but it seems you can't initialize statics with a non-constant.
Comment 11•14 years ago
|
||
Oh, interesting, thanks.
Comment 12•14 years ago
|
||
Mozilla/5.0 (X11; Linux i686; rv:7.0a1) Gecko/20110610 Firefox/7.0a1
Using a range of Unicode box-drawing characters and mathematical operators, you can upgrade to Bugzilla Color Edition™!
││││││││
││││││││
││││││││
││││││││
║║║║║║║║
║║║║║║║║
║║║║║║║║
║║║║║║║║
||||||||
||||||||
||||||||
||||||||
∣∣∣∣∣∣∣∣
∣∣∣∣∣∣∣∣
∣∣∣∣∣∣∣∣
∣∣∣∣∣∣∣∣
⊪⊪⊪⊪⊪⊪⊪⊪
⊪⊪⊪⊪⊪⊪⊪⊪
⊪⊪⊪⊪⊪⊪⊪⊪
⊪⊪⊪⊪⊪⊪⊪⊪
⟒⟒⟒⟒⟒⟒⟒⟒
⟒⟒⟒⟒⟒⟒⟒⟒
⟒⟒⟒⟒⟒⟒⟒⟒
⟒⟒⟒⟒⟒⟒⟒⟒
∐∐∐∐∐∐∐∐
∐∐∐∐∐∐∐∐
∐∐∐∐∐∐∐∐
∐∐∐∐∐∐∐∐
This comment works as a testcase for me. These are all quite distinctly coloured on my screen. It's almost likeable.
Comment 13•14 years ago
|
||
Note that I have my monospace font size set to 16 in Firefox as the default is too small for me. Zooming in and out changes the colours :-)
Assignee | ||
Comment 14•14 years ago
|
||
Whiteboard: [inbound]
Comment 15•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla7
Assignee | ||
Updated•14 years ago
|
Whiteboard: [inbound]
Comment 17•14 years ago
|
||
Confirming that this is fixed for me (compare with attachment 538565 [details]).
Updated•14 years ago
|
tracking-firefox7:
? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•