1449510 - Some fonts are not correctly displayed in print preview mode on https://typekit.com/fonts/acumin

Status: NEW

(Core :: Print Preview, defect)

Description

[roxleitan]

Attachment: print-preview.png

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID:20180327220126

[Affected versions]:
Nightly 61.0a1,Beta 60.0b6

[Affected platforms]:
Windows 10 X64, Ubuntu 16.04 x64

1.Launch Nightly 61.0a1 with a new profile
2.Open https://typekit.com/fonts/acumin
3.Open Print preview

[Expected result]:
All fonts should be correctly displayed

[Actual results]:
Some fonts are not correctly displayed (please see the attached screenshot)


[Note]:
The issue is reproducible also with "layout.css.font-variations.enabled" on False

Comment 1

[Jonathan Kew [:jfkthame]]

They fail similarly on macOS as well, when printing to a PDF and viewing the result with Preview.app.

Comment 2

[Jonathan Kew [:jfkthame]]

FWIW, this doesn't seem to be a recent regression; I see a similar result with a build from late 2015, for example. I suspect there's something weird about how typekit is loading the fonts, but not sure exactly what's going on.

One possibly-related oddity: when using the Element Inspector to examine the font samples, and looking in the Fonts panel, it reports the fonts as being "system", as though they were locally installed. I'd have expected them to show up as "remote" fonts.

And another thing: in my Linux debug build, opening Print Preview for that page fires "ASSERTION: Primary child list can have at most one frame in it" around 20 times.[1]

I'm not sure that has any relevance here, though. I'm more curious about the Inspector believing these are "system" fonts...


[1] https://searchfox.org/mozilla-central/rev/028cd8342899357d80fafba2d528a0fd5819e316/layout/generic/nsCanvasFrame.cpp#202-204

Comment 3

[Alice0775 White]

This bug is affected to not only print preview but also print output.


Regression window:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=aca9840cf06f&tochange=8476f8a5e00b
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=aca9840cf06f&tochange=8476f8a5e00b


Regression window(forcibly set layout.css.font-loading-api.enabled to true):
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=0e9883d2467b&tochange=109ae9a694cc


Regressed by: Bug 1028497

This seems to be implementation level bug of the CSS Font Loading API. And printing feature is broken....