Chromium scales a non-scalable font
Reported by
kyn...@gmail.com,
Mar 8 2016
|
|||||||
Issue description
Chrome Version : 48.0.2564.116 (Developer Build) Built on 8.3, running on Debian 8.3 (64-bit)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Firefox: OK (Iceweasel)
In a nutshell, Chromium insists on scaling a non-scalable bitmapped font (Terminus), even though the font is available in many suitable sizes.
Attached is a comparison between Iceweasel's (left) and Chromium's rendering of the same test page, one where the `style` attributes for all the text-containing items specify `Terminus` as the font-family. (Please click on the image to see it at 100%. The test page's HTML can be seen here: https://gist.github.com/kynnjo/d1c2b75e0903054e0163)
The only size that Chromium gets right is 12px. It looks like it gets the remaining sizes by scaling 12px.
Here are the things I've tried so far, without success.
(OS is Debian.)
(1) I deleted the following symlinks:
/etc/fonts/conf.d/10-scale-bitmap-fonts.conf
/etc/fonts/conf.d/70-no-bitmaps.conf
(2) I added the following symlink:
/etc/fonts/conf.d/50-enable-terminus.conf
(3) I followed the recipe given here http://blog.lazyhacker.com/2014/03/disabling-anti-aliasing-on-chrome.html to inject a custom stylesheet into Chromium, with the following contents:
* {
-webkit-font-smoothing: none;
-webkit-text-size-adjust: none;
text-size-adjust: none;
}
---
Actually, in order to get Chromium to display Terminus *at all*, I had to force it with a pretty heavy-handed `~/.config/fontconfig/fonts.conf` file, shown here https://gist.github.com/kynnjo/e7ff06a3f8fbee01eccd.
---
All the specified sizes are the font's native sizes, as reported by `fc-list --verbose`.
(BTW, the lack of difference between "12px normal" and "12px bold" is to
be expected, since there's no 12px bold in this font. On the other
hand, there *should* be a difference between sizes 14px and 16px, and
between 18px and 20px, since my system has separate font specification
files for all those sizes. So maybe Iceweasel's rendering is not
perfect either. Nevertheless, I'd be delighted if I could get Chromium
to work as well as Iceweasel does here.)
,
Mar 9 2016
,
Mar 9 2016
,
Mar 19 2016
Thanks for the clear and detailed report. We go out of our way to avoid rendering bitmap fonts so this isn't surprising. I'm actually surprised you got it to render at all. Not sure if this is something we'll be able to fix given that a lot of websites depend on fonts scaling smoothly.
,
Mar 19 2016
,
Mar 20 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 21 2017
Closing given the hacks needed to get it to render in the first place. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by kyn...@gmail.com
, Mar 9 2016