Closed
Bug 1388190
Opened 7 years ago
Closed 2 years ago
In Nightly, font rendering is messed up on a few sites. (bad AA)
Categories
(Core :: Graphics: Text, defect, P2)
Tracking
()
RESOLVED
INACTIVE
Tracking | Status | |
---|---|---|
firefox57 | --- | affected |
People
(Reporter: d, Unassigned)
Details
(Whiteboard: gfx-noted)
Attachments
(7 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20170807113452 Steps to reproduce: 1. Go to a website in Nightly, the two that I've tested and confirmed are The Verge (https://theverge.com) and Google Inbox (https://inbox.google.com) 2. Look at the body text on the page. I use infinality & Debian 9 if that matters. The issue doesn't occur on Chrome. Actual results: Blocky, old-looking fonts. Expected results: Smooth font rendering.
Component: Untriaged → Graphics: Text
OS: Unspecified → Linux
Product: Firefox → Core
Hardware: Unspecified → x86_64
Comment 1•7 years ago
|
||
I can't reproduce it on Ubuntu 16.04. Jonathan, do you have any idea about it?
Flags: needinfo?(jfkthame)
Comment 2•7 years ago
|
||
It looks like antialiasing (font smoothing) is turned off, which is generally controlled via system-level preferences or fontconfig settings -- exactly where to find them depends on the desktop environment being used, I guess. I believe Firefox pays more attention to these settings than Chrome, which might explain why things look different there (I wouldn't be surprised if Chrome applies smoothing regardless of OS-level settings). (Also possibly relevant: what specific font is being used, as determined by the Fonts panel in the devtools Element Inspector?)
Flags: needinfo?(jfkthame)
Updated•7 years ago
|
Priority: -- → P3
Whiteboard: gfx-noted
Comment 3•7 years ago
|
||
Same problem. RGB anti-aliasing and hinting don't work on some sites. System settings: anti-aliasing: enabled, subpixel rendering type: RGB, hinting style: slight. System: Kubuntu 16.04.3, 64-bit. Nightly 57.0a1 (2017-09-06).
Comment 4•7 years ago
|
||
Another example. Ubuntu 16.04.3 LTS.
Any chance of running mozregression [1] on this? Sounds like a recent problem. [1] http://mozilla.github.io/mozregression/quickstart.html
status-firefox57:
--- → affected
Flags: needinfo?(s.khoruzhin)
Priority: P3 → P2
Summary: In Nightly, font rendering is messed up on a few sites. → In Nightly, font rendering is messed up on a few sites. (bad AA)
Comment 6•7 years ago
|
||
I can't reproduce this problem using mozregression. But I did some tests. Results are in the picture. System settings of anti-aliasing are work for GUI in all versions of Firefox, but not for sites rendering.
Flags: needinfo?(s.khoruzhin)
This reproduces with a clean profile?
Comment 8•7 years ago
|
||
Yes.
Comment 9•7 years ago
|
||
Comment 10•7 years ago
|
||
Comment 11•7 years ago
|
||
Comment 12•4 years ago
|
||
Do any of the people who were seeing this still have this issue?
Comment 13•4 years ago
|
||
(In reply to Jeff Muizelaar [:jrmuizel] from comment #12)
Do any of the people who were seeing this still have this issue?
Yes. Nothing changed.
Comment 14•3 years ago
|
||
I have also faced font bug problem on this site: https://blogwithjoy.com/
How to solve this?
Flags: needinfo?(hasiburjoy)
Comment 16•2 years ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:lsalzman, since the bug has high priority, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(d) → needinfo?(lsalzman)
Updated•2 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Flags: needinfo?(lsalzman)
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•