Comments on: Typekit now fully supports Opera

By: Martin

Martin — Tue, 17 Aug 2010 10:15:35 +0000

Jeffrey: I’m currently surfing with the most up-to-date pre-release version of Opera from my.opera.com/desktopteam
But I only see the fall-back fonts on http://typekit.com/libraries/trial
Does your browser detection work correctly?

By: Kaptanin Gemisi

Kaptanin Gemisi — Mon, 19 Jul 2010 11:25:00 +0000

Hi Tim –

I’m just not sure why I’m seeing these “Missing Glyphs” appear in Safari Mac and Chrome Mac and Firefox 3.6 Mac — but not Opera for Mac. Is Opera not falling back to fill in the missing glyphs or something?

It would be great if you could note somehow that certain font sets are not complete so we don’t use them on our blogs.

Online İzle

By: Bogdan

Bogdan — Wed, 14 Jul 2010 11:25:03 +0000

That’s really some great news mates!

By: David W. Boles

David W. Boles — Fri, 09 Jul 2010 20:55:15 +0000

In reply to Dustin Wilson.

Thanks for the detailed reply, Dustin. Love your website! Beautiful, funny and magnificently well-designed. A rare find!

Yes, I changed the font on BolesBlues to something a little more “supported” by Opera — meaning substitutions will more gracefully fail, I hope. I now check punctuation and numbers when I do a font type test preview. Gak.

I don’t know why anyone would use Opera if they won’t properly support fallback glyphs. Waste of a browser effort.

By: Jeffrey Veen

Jeffrey Veen — Fri, 09 Jul 2010 16:47:40 +0000

In reply to Dustin Wilson. Yes, that's intentional, Dustin. While we're now serving fonts for Opera, that browser still has some incompatibilities with the Typekit application itself. We're looking into that.

By: Dustin Wilson

Dustin Wilson — Fri, 09 Jul 2010 16:22:31 +0000

Tim,

Incidentally in Opera you’re still displaying a disclaimer at the top of the page after you log in saying that you don’t fully support the browser yet. Is this intentional?

By: Tim Brown

Tim Brown — Fri, 09 Jul 2010 16:08:40 +0000

In reply to David W. Boles. Yes, like I said above, we're considering ways to address fonts with incomplete character sets. See Dustin's reply below about Opera and fallbacks. (Thanks, Dustin!)

By: Dustin Wilson

Dustin Wilson — Fri, 09 Jul 2010 16:03:17 +0000

David,

It looks like you’ve changed the font, but you might be running into a font stack bug in Opera that’s been reported for ages yet not addressed. Both the CSS 2 and CSS 3 specs state (although CSS3 states it in much better and easier to understand language) where if a glyph is missing in the first font in the stack the user agent should go to the next font in the stack and look for it there and so forth. Opera instead drops the entire rest of the stack and falls back to the default typeface which probably in your case would be Times, but in recent builds it’s gotten even worse. It just drops the font stack completely and renders nothing in its place.

What you were probably getting was punctuation rendered in a different typeface and Opera was just not rendering anything due to a bug that should have been addressed years ago.

By: David W. Boles

David W. Boles — Thu, 08 Jul 2010 21:42:20 +0000

Hi Tim —

It would be great if you could note somehow that certain font sets are not complete so we don’t use them on our blogs. Punctuation seems to be a pretty basic need in a font.

By: Tim Brown

Tim Brown — Thu, 08 Jul 2010 21:38:11 +0000

In reply to David W. Boles.

David, these characters are not only missing in Opera, they’re missing from the typeface Hill House. We’re considering a few different ways to address fonts with incomplete character sets. Meanwhile, please know that you’ve done nothing wrong. The glyphs just don’t exist. This is the case for BolesBlues.com, but I’m not sure about your other blogs. Send a note to support@typekit.com with their URLs and we’ll help out.