Issue metadata
Sign in to add a comment
|
Custom Font not rendering, just renders fallback font
Reported by
addbr...@gmail.com,
Apr 15 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.75 Safari/537.36 Steps to reproduce the problem: 1. Visit https://mightybell.com/ 2. Look at first big title 3. Rendering as Helvetica What is the expected behavior? Should be rendering GTWalsheimBold for the big title What went wrong? Our custom font GTWalsheimBold is downloaded, but not applied to elements we specify. Did this work before? Yes Chrome version: 50.0.2661.75 Channel: stable OS Version: OS X 10.11.3 Flash Version: Shockwave Flash 21.0 r0 This is not an issue on the same version of Chrome on Windows, or any other browser on either Mac or Windows.
,
Apr 18 2016
The WalsheimBold web font has only been provided for font-weight 700, the page requests it for font-weight: 800 thus causing a fallback. It should probably fallback on the wrong weight instead or try to synthesize the weight. Likely a bug in Blink. Changing the weight to 700 or changing the font declaration to specify weight 800 makes it work as expected. In general always try to provide web fonts for the weights you use or rendering quality will suffer as synthesized fonts tend to look a lot worse.
,
Apr 18 2016
We are providing a 700 and 800 weight for GTWalsheim. For some reason it looks like Chrome is not downloading the bold version (see attached). Firefox and Safari both download the bold font.
,
May 13 2016
UPDATE: Turns out our CDN was serving the fonts without the "Access-Control-*" headers. We have updated our fonts on the CDN and the issue is fixed now.
,
May 16 2016
Thanks for the update. Closing. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Apr 16 2016