New issue
Advanced search Search tips

Issue 753872 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Amstelvar variation font not working on Windows?

Project Member Reported by bunge...@chromium.org, Aug 9 2017

Issue description

Chrome Version: 62.0.3180.0
Revision: 280223f141c2d
OS: Win10

What steps will reproduce the problem?
(1) Go to http://www.axis-praxis.org/specimens/amstelvar
(2) Note that it renders with "Times New Roman" (which doesn't vary).

What is the expected result?
Should render Amstelvar and vary.

What happens instead?
Got Times New Roman.

Please use labels and text to provide additional information.
All the fonts on axis-praxis seem to work on a recent Linux build of Chromium. On Windows, some of the fonts on axis-praxis specimens work, but others don't (fall back to non-variation fonts).

 

Comment 1 by drott@chromium.org, Aug 10 2017

Thanks for the report. Works for me with Canary 62.0.3181.0 and 62.0.3179 (before updating) with all fonts on axis-praxis.org except Skia and San Francisco since these are referenced as system fonts, which is expected. Is it still reproducible? Does the network panel in DevTools show any loading issues?



I'm actually still getting this with a local build of 64.0.3264.0 . If I look in the console I get the messages

! Failed to decode downloaded font: http://www.axis-praxis.org/fonts/webfonts/AmstelvarAlpha-VF.ttf
! amstelvar:1 OTS parsing error: Not a valid font data

Comment 3 by drott@chromium.org, Nov 13 2017

Now I was able to reproduce this. I think what happens is that the initial decode using DWrite fails because it doesn't like something about this variable font, and then we are not able to detect whether it is a variable font or not, since we never manage to decode it. I have a fix ready for this situation, which I worked on together with Behdad. In this fix we do an initial font blob inspection using HarfBuzz functions, then decide the right instantiator (DWrite/FreeType) after that and use the right SkFontMgr from the start.

Status: Fixed (was: Assigned)
I'm assuming that whatever was wrong is now fixed, since in 64.0.3282.186 everything on axis-praxis seems to work on Windows 10.0.16299.248. Not sure if our code changed or the fonts changed though (I think Amstelvar used to not have a STAT table?).

Sign in to add a comment