Chrome on Android ignores second value in font-family declaration
Reported by
f.con...@gmail.com,
May 3 2018
|
||
Issue descriptionSteps to reproduce the problem: 1. Load the attached file in Chrome on Android. 2. See that the font-family is rendered incorrectly. 3. Test with Firefox Mobile on Android and see how it should be done, in accordance with W3C recommendations. What is the expected behavior? A browser should parse *all* declared values, and only when it doesn't encounter one at all that matches, should it go back to the first fall-back option. What went wrong? Chrome reverts back to the fall back option immediately if the first value is not a match. Did this work before? No Does this work in other browsers? Yes Chrome version: Mobile 66 Channel: stable OS Version: 4.2.2 Flash Version: ? It is a problem that only the mobile Chrome version have. PC versions work OK.
,
May 4 2018
https://android.googlesource.com/platform/frameworks/base.git/+/master/data/fonts/fonts.xml#69 aliases "Times New Roman" to "serfi", which is the first font in your font stack. So there is a match for "Times New Roman" and the text is displayed with serifs, as intended. This works as intended. We do have some font matching improvements planned for Android, see issue 322658 and issue 641861.
,
May 5 2018
No, this does not work as intended by the webmaster! I cannot use a web font if the first-declared font is not available, because Chrome reverts to the fall-back system font immediately!
Another example then. If I declare this:
@font-face {
font-family: 'Verdana Web';
font-style: normal;
font-weight: normal;
src: url('../fonts/verdana-web.ttf') format('truetype');
}
body {
font-family: Verdana, 'Verdana Web';
}
I get Verdana Web in all other browsers on Android, but in Chrome I get the standard sans-serif font, which is a substantially different font!
,
May 6 2018
And even if I do it like this:
@font-face {
font-family: 'Verdana';
src: local('Verdana'),
url(fonts/verdana-web.ttf);
font-weight: normal;
}
body {
font-family: 'Verdana';
}
I get the standard sans-serif font in Chrome on Android!
I am shocked to see how sloppy the responsible Chrome devs are handling the font issues, and with how much disrespect for me, because this is the second time. See https://bugs.chromium.org/p/chromium/issues/detail?id=838662 for the other issue.
From us reporters, a respectful and constructive attitude is required. Why not from the Chrome devs themselves?
|
||
►
Sign in to add a comment |
||
Comment 1 by e...@chromium.org
, May 3 2018Status: Available (was: Unconfirmed)