Android Tofu for Monospace IPA |
||||
Issue descriptionExample URL: https://github.com/googlei18n/noto-source/blob/master/test/LGC/und-fonipa.html Steps to reproduce the problem: See https://github.com/googlei18n/noto-fonts/issues/824 What is the expected behavior? From https://github.com/googlei18n/noto-fonts/issues/824#issuecomment-280129609 : “ There are at least two fonts on Nexus 5x that can render(most of, if not all) the above much better (Roboto and Noto Serif). Chrome should pick up either of them instead of mixing multiple fonts.” What went wrong? See https://github.com/googlei18n/noto-fonts/issues/824 Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? N/A Chrome version: 56.0.2924.87 Channel: stable OS Version: 7.1.1 Flash Version:
,
Oct 27 2017
,
Oct 30 2017
The page in question explicitly sets the font-family to the following "SFMono-Regular", Consolas, "Liberation Mono", Menlo, Courier, monospace; Thus we're required to try all of those fonts, in order, before falling back on a suitable system font with better coverage. We can't just ignore the author specified font and pick a font we think is better. We should, however, find a suitable font for the missing glyphs instead of rendering them as missing. Mixing fonts though is unavoidable with the font-family as specified.
,
Dec 13
|
||||
►
Sign in to add a comment |
||||
Comment 1 by sheriffbot@chromium.org
, Jul 27 2017