Issue metadata
Sign in to add a comment
|
Some codepoints won't render despite fonts providing glyphs being installed
Reported by
g...@gesh.uni.cx,
Jul 13 2016
|
||||||||||||||||||||||
Issue description
Chrome Version : 53.0.2785.8 (Official Build) dev-m (64-bit)
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x: OK
IE 7/8/9: FAIL
What steps will reproduce the problem?
Insert latin subscript codepoints (tested U+2095-U+209C and U+2C7C)
What is the expected result?
Chrome should render the codepoints, especially considering that
system fonts that provide the glyphs are installed (viz. Dejavu).
What happens instead of that?
Chrome displays the "Unknown glyph" box.
Please provide any additional information below. Attach a screenshot if
possible.
Note that if I force Chrome to use Dejavu via the Developer Console,
everything renders fine.
,
Jul 13 2016
Chrome still uses a hard-coded list of fallback fonts on Windows so locally installing a font with the codepoints won't do any good unless you also explicitly specify the font family.
,
Jul 13 2016
Tested on Win10 - seems to work fine. This is likely using the codepath implemented in issue 459056 . Unfortunately, the system API for that codepath is not available on Win7, so this will only work on Win8.1 or later. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ellyjo...@chromium.org
, Jul 13 2016Status: Untriaged (was: Unconfirmed)