Comments on: Rendering Fonts in Today’s Browsers https://blog.typekit.com/2009/09/15/rendering-fonts-in-todays-browsers/ News about Typekit Sun, 01 Aug 2010 19:40:09 +0000 hourly 1 https://wordpress.org/?v=5.4.1 By: Adam https://blog.typekit.com/2009/09/15/rendering-fonts-in-todays-browsers/#comment-1029 Sun, 01 Aug 2010 19:40:09 +0000 http://blog.typekit.com/?p=233#comment-1029 Great post. I wish there were less issues with browser compatibility.

]]>
By: Matt Cassarino https://blog.typekit.com/2009/09/15/rendering-fonts-in-todays-browsers/#comment-1028 Tue, 15 Jun 2010 17:25:13 +0000 http://blog.typekit.com/?p=233#comment-1028 I’m with Trevor and unfortunately this issue still exists as of June 2010. While I’d love to use your fonts, the font “shifting” is just too noticeable and distracting.

]]>
By: Yadira https://blog.typekit.com/2009/09/15/rendering-fonts-in-todays-browsers/#comment-1027 Fri, 21 May 2010 07:35:25 +0000 http://blog.typekit.com/?p=233#comment-1027 Great stuff!! All working wonderfully,Jacarri

]]>
By: Gabriel https://blog.typekit.com/2009/09/15/rendering-fonts-in-todays-browsers/#comment-1026 Fri, 21 May 2010 07:35:02 +0000 http://blog.typekit.com/?p=233#comment-1026 Thank you.It is grate This is cool,Jacarri

]]>
By: Rabia https://blog.typekit.com/2009/09/15/rendering-fonts-in-todays-browsers/#comment-1025 Fri, 21 May 2010 07:34:39 +0000 http://blog.typekit.com/?p=233#comment-1025 Great idea!,Jacarri

]]>
By: Trevor Burnham https://blog.typekit.com/2009/09/15/rendering-fonts-in-todays-browsers/#comment-1024 Fri, 25 Dec 2009 03:57:26 +0000 http://blog.typekit.com/?p=233#comment-1024 The flicker when the original font is replaced by the TypeKit font is the one factor preventing me from embracing TypeKit. I’d love to keep my text from appearing until the fonts have loaded (subject to some maximum delay time in case TypeKit service is interrupted), and in this post you mention hooks that might let me do that, but I haven’t seen anything else on the subject since.

I hope that you’ll make a priority of this feature. And if there’s a way for us JS coders to do this already, please let us know!

]]>
By: Anthony Calzadilla https://blog.typekit.com/2009/09/15/rendering-fonts-in-todays-browsers/#comment-1023 Fri, 11 Dec 2009 20:17:32 +0000 http://blog.typekit.com/?p=233#comment-1023 Interesting read

]]>
By: SNEAKY FREAKY https://blog.typekit.com/2009/09/15/rendering-fonts-in-todays-browsers/#comment-1022 Sat, 07 Nov 2009 23:33:57 +0000 http://blog.typekit.com/?p=233#comment-1022 I don’t know anything really about your service yet, but after reading this post I suggest making the text first load as a common font (ARIAL etc) and then when the fancy font is loaded, change the text to that font. Not a perfect solution of-course, but just an idea.

]]>
By: Brian Birtles https://blog.typekit.com/2009/09/15/rendering-fonts-in-todays-browsers/#comment-1021 Wed, 07 Oct 2009 22:38:18 +0000 http://blog.typekit.com/?p=233#comment-1021 So you have servers on every continent—does that include Australia? Some people like to argue Australia is just a big island (but I think officially it’s a continent and Greenland is the world’s biggest island). I’m impressed if you’ve got servers here too.

If you’re testing wacky fonts, you should try the fonts that come bundled with fudemame: http://fudemame.net/
I know others have had trouble with those fonts, although I think it’s mostly the name tables on those fonts that have been the issue.

]]>
By: Mauro Ramón https://blog.typekit.com/2009/09/15/rendering-fonts-in-todays-browsers/#comment-1020 Sat, 19 Sep 2009 01:19:16 +0000 http://blog.typekit.com/?p=233#comment-1020 I agree completely with Enrique R.
To get lower hits on Google, or worse than than, getting a “This page has xx errors” on xhtml validator at w3.org, it´s not an option.
When following a new path towards better designs (and development improvements), the way is forward… not moving in circles.
Good idea to the “Best practices” approach. My two cents, imho.
Cheers to the typekit team!!

]]>