New bug in Chrome v33 affecting web fonts

Chrome 34 was released on 08 April 2014 and includes a fix for this disappearing web font bug. If you continue to see issues with Typekit fonts after upgrading to v34, email and we will look into it.

Version 33 of the Chrome browser was released on February 20, 2014, and includes a fix for the disappearing web font bug we reported earlier.

Unfortunately, a new bug was introduced in version 33, where web fonts may not be displayed until the user interacts with the browser window (scrolling or clicking), causing the browser to redraw the page. The Chrome team is aware of the problem and is working on a fix.

Update, 05 March: we have confirmed that fonts loaded from Typekit are affected by this bug, but the way in which the Typekit JavaScript works makes it less likely that our customers will encounter the problem. (Again, this bug affects all web fonts, not just those served from Typekit.)

We have tested some possible workarounds, but determined that there is not a solution which we are comfortable including in the Typekit JavaScript for all users to download. The Chrome team has a fix for the bug which should be available in the next browser update, and we feel that the best approach is to wait for that update.

Users have posted some suggested workarounds for the problem in the comments on the Chrome bug thread, if you would like to explore the options for your own website.

If you believe that you are seeing this bug on a website that loads fonts from Typekit, please email us at and we will be happy to look into it.

Liz Galle

Typekit Support. When I’m not helping our users get the most out of Typekit, I plan blog posts and try to get better at Keynote. I live, work, & knit in Cambridge (MA), prefer Marvel to DC, and love snow.

Sites We Like: Emily Brick & Katie Christ

Sally Kerrigan · February 28, 2014 · Using Type

New on Typekit: Lust Script, Clavo, Sharik Sans, & Adriane Text

Sally Kerrigan · March 5, 2014 · Fonts on Typekit