SAVE 25% when you purchase our Theme Bundle and Make Plus together. View bundle deal.

Chrome 33 Webfont Fixer

By Zack Tollman on April 1, 2014

In all of our themes, we use Google Fonts or Typekit fonts to give our designs beautiful typography. Unfortunately, Google’s Chrome browser has had some issues displaying webfonts recently. These issues have caused display problems in some of our themes in some circumstances.

When the bug is present, any text that is styled with a webfont, will not appear. The Chrome bug affects version 33 of Chrome. This is a problem that affects all webfonts and is not unique to WordPress or our themes.

The Chrome team will likely fix this bug in Chrome 34 or 35. Until the bug is actually fixed, website owners can apply some extra CSS to their sites as a temporary workaround. To assist our customers, as well as other WordPress users that are experiencing this problem, we have prepared a simple plugin that adds the CSS workaround to any WordPress theme. We believe that this plugin is a better stopgap than patching all of our themes because this solution is a temporary workaround and we do not want to add it as a permanent part of our themes.

Did you know that Surf Office, Postmatic, Yeah Dave, and over 700,000 small businesses run their websites with Make, our free WordPress page builder. Discover the Make page builder now.

To install this plugin, please follow these instructions:

  1. In your WordPress admin, go to Plugins → Add New
  2. In the search input, search for chrome 33 webfont fixer
  3. Click Search Plugins
  4. Locate the plugin named Chrome 33 Webfont Fixer
  5. Click Install next to the Chrome 33 Webfont Fixer plugin
  6. Click OK in the prompt window
  7. Click Activate Plugin

If you wish to install the plugin manually, you can find it on the WordPress plugin directory or Github.

With this plugin installed, your fonts should display normally. Please let us know if you have any questions about this bug.

One Response

  1. Mark Root-wiley

    Just for reference, this issue was marked as resolved and closed on 20 April 2014.

Comments are closed.