Comments on: Font events: Fallback fonts and styles https://blog.typekit.com/2010/11/02/font-events-fallback-fonts-and-styles-2/ News about Typekit Fri, 12 Nov 2010 18:59:34 +0000 hourly 1 https://wordpress.org/?v=5.4.1 By: Sean McBride https://blog.typekit.com/2010/11/02/font-events-fallback-fonts-and-styles-2/#comment-1968 Fri, 12 Nov 2010 18:59:34 +0000 http://blog.typekit.com/?p=1924#comment-1968 In reply to nimbupani.

Thanks for the pointer to the Code Styles resources! Their font stack builder is really helpful, and their data on font installs across platforms makes choosing fallback fonts much more data-driven. I added an update to the post so people can check it out.

]]>
By: nimbupani https://blog.typekit.com/2010/11/02/font-events-fallback-fonts-and-styles-2/#comment-1967 Fri, 12 Nov 2010 13:45:38 +0000 http://blog.typekit.com/?p=1924#comment-1967 In reply to nimbupani.

Luke: W3Schools is *truly* a disgrace. It exists to fill a void between ignorance & clicking the first result in a search.

Where is the evidence for W3School’s list of websafe fonts? How do you know those are facts? Code Style’s at least has an open font survey that anyone can submit (pity it runs on Java Applet though).

]]>
By: Luke Sheppard https://blog.typekit.com/2010/11/02/font-events-fallback-fonts-and-styles-2/#comment-1966 Fri, 12 Nov 2010 11:36:27 +0000 http://blog.typekit.com/?p=1924#comment-1966 In reply to nimbupani.

A sacrilege?? That’s a bit strong isn’t it? W3Schools has done some pretty amazing work over the years – I realise that they may have fallen out of favour recently but I think they deserve some credit in terms of the work they have done – obviously you’ve forgotten how much of a nightmare it was before they existed??

As for the link you provided, it’s useless, considering it gives not indication of cross-OS compatibility anyway. A list of commonly installed fonts does NOT constitute a list of web-safe fonts.

]]>
By: Steven Scarborough https://blog.typekit.com/2010/11/02/font-events-fallback-fonts-and-styles-2/#comment-1965 Tue, 09 Nov 2010 18:52:19 +0000 http://blog.typekit.com/?p=1924#comment-1965 In reply to Steven Scarborough.

Thanks! It all made sense after I read the previous posts about EVENTS & FOUT. I checked out your stylesheet and it then became crystal clear. I think it must have been my connection that displayed Georgia instead of Lapture. What a great example of your post!

]]>
By: Sean McBride https://blog.typekit.com/2010/11/02/font-events-fallback-fonts-and-styles-2/#comment-1964 Tue, 09 Nov 2010 18:40:07 +0000 http://blog.typekit.com/?p=1924#comment-1964 In reply to Steven Scarborough.

That’s unusual. The fonts work as expected in my copy of Safari 5. It’s possible that you have a preference that’s disabling web fonts or JavaScript in that browser? You can shoot an email to support@typekit.com if you’d like.

I’m using the .wf-active class in my own stylesheet for the website, which in this case is at http://www.rimrockcollegeconsulting.com/styles.css . Check out the references near the top of the stylesheet.

]]>
By: Steven Scarborough https://blog.typekit.com/2010/11/02/font-events-fallback-fonts-and-styles-2/#comment-1963 Tue, 09 Nov 2010 18:24:57 +0000 http://blog.typekit.com/?p=1924#comment-1963 I checked out http://www.rimrockcollegeconsulting.com using Safari 5, but I was served Georgia instead of the Lapture font I expected.

How/where are you using the .wf-active class? Is it placed in the TypeKit stylesheet? I’ve tried something similar, but couldn’t get the browser to use the fall back styles.

Thanks!

-Steven

]]>
By: nimbupani https://blog.typekit.com/2010/11/02/font-events-fallback-fonts-and-styles-2/#comment-1962 Wed, 03 Nov 2010 23:38:09 +0000 http://blog.typekit.com/?p=1924#comment-1962 Oops, left the comment on a wrong post! This is the post I wanted to comment on 😐

It seems a sacrilege for a respected blog to give credence to W3Schools. I think Code Style’s Most Commonly Used Fonts is a much better reference.

]]>
By: Sean McBride https://blog.typekit.com/2010/11/02/font-events-fallback-fonts-and-styles-2/#comment-1961 Wed, 03 Nov 2010 18:01:46 +0000 http://blog.typekit.com/?p=1924#comment-1961 In reply to Darren Ansley.

font-size-adjust is a part of the current CSS3 working draft, and it’s a great tool for matching the x-height (the height of lowercase letters) of a font with fallback fonts. Unfortunately, it’s only currently supported in Firefox. In addition, depending on your design, you may want to adjust more than just font-size when fallbacks are used. In my example, I also decided to adjust line-height. Font events work today in all browsers that Typekit supports and allow you to adjust any CSS property.

]]>
By: Darren Ansley https://blog.typekit.com/2010/11/02/font-events-fallback-fonts-and-styles-2/#comment-1960 Wed, 03 Nov 2010 16:14:23 +0000 http://blog.typekit.com/?p=1924#comment-1960 What about using font-size-adjust? Do you consider using this approach a better solution?

]]>
By: Joe Golike https://blog.typekit.com/2010/11/02/font-events-fallback-fonts-and-styles-2/#comment-1959 Wed, 03 Nov 2010 15:25:22 +0000 http://blog.typekit.com/?p=1924#comment-1959 The generic serif or sans-serif should be the default fallback. The only time I would include another option to fallback to before the generic would be when something like Georgia more closely matches your intended web font. Never specify Arial and then sans-serif, or you create a situation where Mac users will get Arial instead of Helvetica

]]>