1394127 - Zilla Slab not used for rendering

Status: RESOLVED WORKSFORME

(Core :: CSS Parsing and Computation, defect)

Description

[Michael Kohler [:mkohler]]

With today's Nightly (also yesterday's Nightly), in the following testcase the "Zilla Slab" font is not used to render to heading, even though it gets downloaded. It works perfectly well in Release with the same testcase. 

https://michaelkohler.github.io/bug-testcases/2017-08-26_nightly-google-font-zillaslab.html

Additionally, when I download the font and use @font-face to embed it, it works perfectly fine. Might be a Google Fonts problem, however, downloading the same font from Google Fonts and use it with @font-face, it works as well.

Setting layout.css.servo.enabled to false does not change anything.

Comment 1

[Selena Deckelmann :selenamarie :selena]

Jet -- let me know if this was the wrong component.

Comment 2

[Jet Villegas (inactive)]

The test file returns the following errors in the console:

Blocked loading mixed active content “http://www.sfgate.com/css/hdn/fonts/sofia/SofiaProBold-webfont.woff”
Blocked loading mixed active content “http://www.sfgate.com/css/hdn/fonts/league-gothic/league_gothic-webfont.woff”
Blocked loading mixed active content “http://searchfox.org/static/fonts/icons.woff?2013”
Blocked loading mixed active content “http://www.sfgate.com/css/hdn/fonts/euclid/EuclidFlex-Bold-WebXL.woff”

Note that the above are URLs for web fonts from pages in other browser tabs ^ and not the expected font URLs used by the CSS:

/* latin-ext */
@font-face {
  font-family: 'Zilla Slab';
  font-style: normal;
  font-weight: 400;
  src: local('Zilla Slab'), local('ZillaSlab-Regular'), url(https://fonts.gstatic.com/s/zillaslab/v2/Rqj61QmcYU88jfBZybBYtQsYbbCjybiHxArTLjt7FRU.woff2) format('woff2');
  unicode-range: U+0100-024F, U+1E00-1EFF, U+20A0-20AB, U+20AD-20CF, U+2C60-2C7F, U+A720-A7FF;
}

Jonathan: is this a font or networking issue? Thx!

Comment 3

[Jonathan Kew [:jfkthame]]

Strange.... I can't seem to reproduce the problem here. On the testcase, the Zilla fonts appear fine for me.

(The issue sounds very much like the known Google Fonts subsetting bug, whereby they would often serve invalid resources for subsetted fonts; on Nightly, we validate and reject those resources, while on Release we are more forgiving and allow them to load. But in this case I can't reproduce the failure, even though validation is enabled.)

There may have been some recent fixes in this area on the Google Fonts side; are you still seeing the problem currently?

Comment 4

[Michael Kohler [:mkohler]]

No, I can't reproduce this anymore, neither in today's Nightly nor in the Nightly I reported it for. Seems like this was fixed on Google's side.