Unable to repro this issue on Windows 7, 8.1 & 10 for Google Chrome Stable Version - 52.0.2743.116

Screen-shot is attached.

@valtere.ttc: Could you please perform the steps mentioned beneath and let us know your observations.

1. Update your Google Chrome Stable Version - 52.0.2743.116
2. Re-test the same on a clean profile [chrome://settings -> Add Person -> Do not Login]

Thank you.

Deleted: 641861.png 343 KB

	641861.png 343 KB View Download

Hallo,

When I see at the picture that you sent to me. I can determine  directly, that the
font that is used isn´t Akzidenz-Grotesk BQ but Times New Roman.
Also, I did what you said. That  doesn´t work always.
But the problem is now very important and criticism, please try to find a solution.
Here is the screenshot from the view of Explorer and Google Chrome.

Thank you.

Deleted: Screenshot_Example.png 60.0 KB

	Screenshot_Example.png 60.0 KB View Download

We have the same problem; we use the font-family Avantgarde. In this debug view Chrome list the right font, but the text is rendered with the font family times. Do you think it's a Bug?

I add two Screenshots on with Chrome with the wrong font and on with the Internet Explorer with the correct font.

Deleted: ChromeWithWrongFont.png 55.1 KB

	ChromeWithWrongFont.png 55.1 KB View Download

Deleted: IEwithCorrectFont.png 9.6 KB

	IEwithCorrectFont.png 9.6 KB View Download

After I update Chrome to Version 53.0.2785.116 it is still the wrong font family. It was possible that Chrome use the right font family, if I use the flag disable direct write. But you remove this Option.

Thank you for providing more feedback. Adding requester "rnimmagadda@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

One thing I notice is that the font is no TrueType font it is an otf font. Does Chrome supports this type of Font? Or did somebody else find out something? That's a huge problem for use.

Able to repro this issue on Windows 7, MAC (10.11.6) & Ubuntu Trusty (14.04) for Google Chrome Stable Version - 53.0.2785.116

This is a Non-Regression issue existing from M30 - # 30.0.1549.0

Deleted: 641861.mov 4.3 MB

641861.mov 4.3 MB Download

Correction - Chrome Stable Version Tested On - 53.0.2785.143

Could you provide a copy of the Avantgard or "Akzidenz-Grotesk BQ" fonts that do not render? I am suspecting these might be Type-1 font files which are not supported. Where did you get the original fonts in question, what is the source for those?

Hi,

the font I have problems with is 'AvantGarde CondBook'. I send you all my AvantGarde Fonts. The Font must be in the file IT020_.ttf in the zip file.

So I think, it is not a Type-1 Font.

Deleted: AvantGardFonts.zip 306 KB

AvantGardFonts.zip 306 KB Download

I get the font from a customer from us. 

This font has different spellings in the name table (ttx table dump attached) and we may be matching on a different one than Internet Explorer or Firefox. I would need to check in more detail, what's the correct approach and what our current behaviour is, a quick check on Linux and Mac shows: Linux matches against the family name, name record ID 1, and on Mac we match against the PostScript name, namerecord ID 6. 

You should be able to access the font if you use both spellings in one font-family style rule, e.g:
font-family: AvantGarde CondBook, AvantGarde-CondBook;

Hope this helps as a workaround for now, thanks for the report.

Deleted: namerecord_dump.txt 4.2 KB

namerecord_dump.txt 4.2 KB View Download

Hi,

thanks for the answer. I tried it with the name AvantGarde-CondBook, but it is still the wrong font. 
Do you believe, that this problem gets solved to the next release of Chrome next month?
Does it work on Linux or Mac?

How did you produce the file namerecord_dump.txt? 

The dump was produced by running the ttx tool from https://github.com/fonttools/fonttools on the IT020_.ttf file and extracing the name table.

This issue requires further analysis, the workaround I suggested worked at least on Linux and Mac, I have so far not tested on Windows. We don't currently have a fix for this issue and I can't give an estimate in which version this will be addressed.

Another workaround at the moment might be to use the font as a web font:
@font-face {
font-family: avantgardecondbook;
src: url("IT020.ttf");
}

.mystyle {
font-family: avantgardecondbook;
}

Fontconfig recently added FC_POSTSCRIPT_NAME which might come handy here.

Thank you for the tip with font-face that works on windows

It is not correct for the font-family property to match against PostScript font face names. The CSS Fonts spec is quite clear that "a font family name only specifies a name given to a set of font faces, it does not specify an individual face",[1] whereas a PostScript name (id 6) uniquely identifies a specific face, NOT a family.

Simple testcase that demonstrates the incorrect behavior on macOS:

data:text/html,<div style="font-family:Times-BoldItalic, sans-serif">should be sans serif

This example should NOT render as Times Bold Italic, but it does.

Reports suggest (I have not tested) that this incorrect use of the PostScript name may affect Chrome on Android as well.

[1] https://drafts.csswg.org/css-fonts-3/#font-family-prop

Agree, thank you. See also issue 627143 for the reverse problem.

drott@ This has come up as one of the top recurring issues in our Firefox / Google Search compat effort (https://docs.google.com/document/d/1j6vEd-lsB8SZF55xsa6QTr48JJLRtoYwqy2SLrAUdeM/edit#).

Ignoring the web compat risk, would this be hard to fix?

I am now actively working on the reverse issue 627143, where matching local() is incorrectly performed against family names, instead of postscript names. I can add this issue here to my testing and straighten out both of them.

Can you clarify which one is higher priority for the web compat efforts?

As far as I can tell from my test, the Roboto-Regular on android does not in fact work. I think we only get Roboto because of the sans-serif fallback.

Chrome on MacOS only and Safari are the only browsers which match the postscript names from my demo (Used Verdana as another backup alternative font which is available on most platforms):
https://jsfiddle.net/flackr/04617p3v/27/show/

To clarify for #23, the Roboto-Regular seems to have no effect on Android, we only get Roboto because the default sans-serif font on Chrome Android is Roboto, so this issue shouldn't be blocking that. It also shouldn't be risky to remove this behavior since as far as I can tell it only happens on Mac.

flackr@ and I made an interesting additional discovery. On Chrome Android only, the font-family name 'sans-serif-medium' is accepted as a valid font and results in a rendered glyph of "Roboto Medium".

serif-medium, cursive-medium etc do not work, it is just 'sans-serif-medium'.

We attempted to verify whether postscript names work for system fonts on Chrome Android, but were unable to find *any* installed fonts. Not even trying to target the underlying "DroidSans Mono" etc worked, they didn't match in any configuration we could find.

Firefox Android did not recognize sans-serif-medium as a valid font-family.


This does not affect the 'Roboto-Regular' discussion, we still only get Roboto because sans-serif (the fallback) on Android is Roboto.

re #26, I found https://stackoverflow.com/questions/19691530/valid-values-for-androidfontfamily-and-what-they-map-to which implies that Android actually ships font-families named 'sans-serif-medium', 'sans-serif-italic' etc. I'm not 100% sure if android:fontFamily is the same concept as the web font-family, but if it was it would explain the behavior there. (And would mean the postscript bug still doesn't exist on Android).