New issue
Advanced search Search tips

Issue 840677 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 11
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

[Missing Test]: PDF looks terrible, but fine in Firefox

Project Member Reported by viswa.karala@chromium.org, May 8 2018

Issue description

Automated tests for the below commit have been missing.Would it be possible to add test coverage to avoid regressions in future?

CL: 
----
https://chromium.googlesource.com/chromium/src.git/+/5e4114c0275b6182f40f82a2ea94ed9c009baaa5

Ref Bug: 
---------
https://bugs.chromium.org/p/chromium/issues/detail?id=811110

Thank you.
 
Components: -Blink>Fonts
Status: WontFix (was: Assigned)
It isn't really possible to add a test for this, since the issue was that the specific fonts require hinting in order to be legible at all. FreeType keeps a list of signatures of these sorts of fonts and the resolution to the issue was to add the fonts to that list. There isn't any way to test for unfortunately designed fonts which might be created and used in the future. All this is to say that there wan't really any bug in the original issue, the font was being rendered exactly how it should be and the fonts themselves are to blame. However, we try to make these essentially broken existing fonts render as well as we can for users who were unfortunate enough to need to use them but still discourage further production of such fonts.

In theory we could write a better detection algorithm than a blacklist in FreeType, but this would be an extra font analysis step for an extremely rare case. We also don't really want to encourage more of this sort of font to be created in the future, since there are much better ways to create composite glyphs in OpenType than relying on hinting instructions.

Sign in to add a comment