I added the suggested backup fontstack of Helvetica, Arial, sans-serif; in the fallback field for my fonts.com font, but the fontstack is not listed in the css declaration as you can see in the screenshot attached.
(The primary Helvetica Bold font is not loading at all in IE9 which is another problem, but for some reason the fallbacks aren't either.)

CommentFileSizeAuthor
font stack issue-4.png201.81 KBKendall Totten
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

sreynen’s picture

Status: Active » Postponed (maintainer needs more info)

Can you look in your font.css file and see if that includes the fallbacks? What I'm seeing on my local test is that the fallbacks are correctly added to the font.css file, but that's be overridden by the CSS coming from fonts.com, which does not include fallbacks. I'm not sure if there's anything we can do about how fonts.com does that, but the first step either way is to confirm that's what's happening in your case.

Diane Bryan’s picture

This may not be an exact duplicate of the issue I'm tagging onto, but by the title it appears to be.

I am rebuilding a site from scratch on a new host. I'm using AdaptiveTheme. In AT's interface I entered a default font-stack for all my text, which is basically a sans-serif stack. I built the first ten pages of the site, a bunch of content types, image types, etc. Maybe half the site's content is now displaying.

In this un-@fonted state, the site's fonts are instantly available, per the default font-stack, all sans-serif.

THEN

I enabled @font-your-face, used my typekit key, and pulled in 5 font variants to handle all text on the site. Now, before any page loads, there is a noticeable lag and FOUT (flash of unstyled text) in serif.

Why serif?

Before I enabled @FYF it was sans-serif, and I had instant fonts. These still show up in Firebug as being overwritten by @FYF with my typekit fonts. But the FOUT is serif.

Somehow @font-your-face is either forcing the site to fail to load my default fonts until it's ready to display the typekit fonts, or it is overwriting the default, without that being apparent in Firebug.

Do you think Typekit could be overriding my default somehow? If so, wouldn't I see my theme default until typekit has loaded?

Neslee Canil Pinto’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (outdated)