Typekit Browser Support

Thanks for the clarification. Could you add a section on mobile browser support as well?

I'm using Firefox 3.5.2 in Linux and I get the red bar telling me I'm using an unsupported browser. Here's my browser string: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2

Darn. I wish I would've read that before throwing-down $50.
I was pretty much giddy to throw money at such an awesome project, and after reading that IE5 & later supports @font, I didn't think twice about paying.

Now I'm thinking twice about paying. Not good.

Ok, after ACTUALLY USING the app :-) things are much better.
I did final tweaks to the CSS sans-typekit, so that my fallback would be solid. Of course, this is the obvious thing to do with any JS.

Typekit is just amazing guys. 3 hours later, I'm completely sold.

Would it be too much to ask to support Google Chrome? It is after all just as capable as Safari (if not moreso...)

Please stop using browser detection. If you must use some kind of detection, use RENDERING ENGINE detection. Typekit.com thinks that Shiretoko (Firefox 3.5.x's nightlies) and Namoroka (Firefox 3.6.x's nighlies) don't support @font-face when they do. Just parse the Gecko/VERSION_HERE string to see if a Mozilla-based browser supports @font-face. Many browsers are built on top of Gecko and that is why it should be the Gecko version you're checking for not the "Firefox" version.

Hi, why isn't Opera supported? Opera 10 supports @font-face so is there some other reason?

Firefox 3.5.3 on Ubuntu Linux. Typekit actually works just fine, but the unsupported browser warning bar still appears.

The Editor works fine yes but you can't preview fonts in your page as they don't display, well they don't on mine or my work machine.

I have to switch to another computer (an ageing G4 mac) just to see if my code is working...annoying seeing as its the same browser on both just the stupid OS check that breaks it.

http://dev.opera.com/articles/view/th...

While I understand the urge to be up front about how typekit can be used, browser detection based messages make me sad. Especially when they aren't applicable to me, and haven't been for at least a month. I know it's a pain but if you're going to go to the trouble of listing off what IS supported, then you're pretty much obligated to stay current with browser development.

is there a timeline on internet explorer? more than one persons that use the internet use IE

Any updates on the possibility of changing from browser detection to rendering engine detection (mentioned above by Elijah Grey)?

Seems like a good choice and would open Typekit up to a whole load of new users.

what about iPhone support? or does mobile safari not support font-face

On my tech-focused site, I expect to have a much larger proportion of Linux users than the net-wide average. Most won't be able to see the fonts I just paid to use because TypeKit still uses user-agent checking on the client side.

I'm thrilled about TypeKit, but I can't use it until this is fixed.

Hey folks, me too , I'm getting the redbar with firefox on Linux version ( 3.5.4 )

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091028 Ubuntu/9.10 (karmic) Firefox/3.5.4

How do I can fix this?

defferent font shows in FF3 and defferent in IE7 (i thin EI7 is the right one)

Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2b1) Gecko/20091029 Firefox/3.6b1

Red bar showing for me.

Agree with William, apparently Firefox 3.5 or higher doesn't include pre-release versions of 3.6, getting the red bar saying my browser isn't fully supported.

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2b1) Gecko/20091029 Firefox/3.6b1

Did you see:

http://paulirish.com/2009/bulletproof...
Method Supports Chrome (Pre-V.4).

http://www.fontsquirrel.com/fontface/...
Great font-face builder tool.

Typekit is awesome!

As @tmtstr wrote, Chrome supports @font-face with SVG fonts as of Chrome 0.3+.
See: http://paulirish.com/2009/bulletproof...

Will Typekit soon have SVG fonts to support Chrome?

Not being able to serve Chrome users is a showstopper, because Chrome market share is growing at a good rate and is >5% for some sites.

Is it too much to ask for you to publish a table summarising Typekit support across all common browsers and platforms, on the Typekit site? It's very frustrating to have to amalgamate the complete picture from the comments here and elsewhere around the web.

For an example of why I find the picture confusing, why does Bello Pro render correctly on the typekit.com homepage in IE6 and IE7, but Skolar on forabeautifulweb.com (a site participating in your technology trial) doesn't? Why is Bello Pro on your homepage a background image in Firefox 2 or 3.0? Doesn't it give a misleading impression that those browsers are supported? Does Typekit generate background images if necessary?

I am very keen to start using Typekit, but right now I can't give my clients assurances as to when it'll work and when it won't.

IE support ?

Does it help that much on the S.E.O front? Are Images that bad?? $250 p.a erm.......

I'm having problems with FF3.5.5 on Mac. Custom fonts disappear after the browser is opened 2nd time. Fonts reappear only after clearing the cache?

any reason (besides its a trial account) that type sometimes renders aliased - Safari 4.0.4? if it IS a trial account thing only, please let me know.
thanks,
Peteski
http://thisisnthappiness.com/

Hi all,

First of all, thank you developers for bringing up Typekit, it looks like it'll be an awesome system even for putting up already free-fonts on our websites with improved performance! On the other hand I realize it still on it's early days and lots of things need to be fixed for it to be consistently usable.

I read about the many issues with different versions of Firefox (that use the Gecko/Mozilla engine) that are not working with Typekit though they fully support the @font-face declaration and I would like to stress out the same thing with Webkit (read Safari) based browsers.

Great Web/CSS design applications like CSSEdit or Expresso that are based on the Webkit engine and fully support the @font-face declaration don't work with Typekit because of the browser checking issue.

Please use rendering engine Checking if it's needed! :)

One question, why is Browser checking so necessary? If a browser doesn't support @font-face why not let the Browser itself fall back to the next font on the Stack??

Keep up the work it's gonna come out great!

The verbiage throughout your site is very misleading as to what is supported and what isn't. Take this page for example: http://getsatisfaction.com/typekit/to...

The first paragraph says, "We plan to support other browsers, including Internet Explorer, in a future release."

While the very next one says, "The Typekit fonts you use on your website will render in most browsers that support the CSS @font-face rule, including Firefox 3.5 and higher, Safari 3.1 and higher, and Internet Explorer 6 and higher."

It's been over three months since comments were posted about switching to rendering engine detection rather than browser based detection and I kept asking myself the same thing over and over while reading through comments... Theo beat me to it:

"One question, why is Browser checking so necessary? If a browser doesn't support @font-face why not let the Browser itself fall back to the next font on the Stack??"

And another comment from fjordaan in another post:

"Is it too much to ask for you to publish a table summarising Typekit support across all common browsers and platforms, on the Typekit site? It's very frustrating to have to amalgamate the complete picture from the comments here and elsewhere around the web."

+1 For both of these. I think if these were both done you would really, really be onto something. The faster your service works as intended in all browsers the faster you'll see success as a company.

Hey Greg,

I'm testing now with Google Chrome on a local virtual machine on my mac.

The @font-face declaration works when I use local fonts or when I try to see pages such as http://www.fontsquirrel.com/fontfaced...
But doesn't quite work with Typekit.
It also doesn't work when I try to view a page like but IE doesn't also: http://dl.dropbox.com/u/39519/webfont...

I have Chrome v3.0.195.33 running on Windows XP installation on my mac.

Should this be working at all? Any thoughts?

Just trying to help on debugging...

best,

t.

Running in Firefox 3.0.15, the TypeKit JS is loading, but obviously the fonts aren't being rendered.

Should browsers that aren't supported still be loading up the JS like this, or do I need to duplicate my font stack in the TypeKit application? (that seems silly).

-Rob

Let me get this straight - only two browsers are capable of showing the sample preview library of the fonts on offer! That's not exactly a clever way to inspire me to use this system is it? Like the majority of people I wish to view the fonts as a typical user would, with common and last version browsers, not as an up to date techy geek user would. I arrived inspired and left feeling disappointed, not sure whether to even try the free trial.

I just spent money on TypeKit only to find that it doesn't work in the browser I use.

I'm using FF 3.5.6, I get the red bar saying it is not supported! At least I just signed up for a trial and didn't put out any cash

I am having difficulties using a Windows XP 64 bit operating system on most browsers, even if I have the latest when previewing your Library page it shows the message "You're using a browser that Typekit doesn't yet fully support. Read more..." at top.

I know that Wondows XP64 bit is not very popular and it has some issues with sIFR as well but are you planning on any updates in relation this?

Hi there,

I'm trying out Typekit for the first time and tried the steps shown on: http://typekit.com/help/wordpress, but the fonts are not showing up on my webpage (http://juliofromny.wordpress.com).

I'm currently using the "Andreas09 by Andreas Viklund" theme. Could this theme be the reason the fonts aren't showing, even though the "colophon badge" is showing up with no problem?

Please assist. Thanks

Hi Julio

Looking at your kit I can see you don't have any of the selectors present and so Typekit, though operating, doesn't know what to modify. Here's an excerpt from our Wordpress help page.

"Adding fonts

As you browse around Typekit, you'll see a button labeled "Add" next to each font. If you see a font you'd like to try, just click that button and the Editor will open in a new window. You'll see the font you chose, along with some features that let you control how the font will work on your blog.

Click on the font and open up the Selectors area on the left. Selectors are a term from HTML and CSS that describe how a page is constructed. If you haven't used these technologies before, don't worry -- we'll walk you through it. Let's try now with a simple example: Adding the font you just chose to your blog's headline.

In a new browser window, navigate to one of your blog posts. Once you're there, use your browser's view source feature to see the page code. There will be a lot of code in there, but if you scroll down you'll eventually find your post's headline. Or, it might just be easier to search for the headline text in the source. See the h2 tags around it? That's what you need to enter into the selector area (without the angle brackets, though.) Just type h2 into that form and hit enter."

The idea is to find the HTML tag that surrounds the text you want to change and then enter it in to the Selector Box. If you use your browser's "View Source" command, you'll see a bunch of fairly messy looking code, but if you search for the text of, say, your headline, you should find something like this:

<h1>This is my headline text<h1>

To apply a font, you'd open the Editor in Typekit, select the font you want, and enter "H1" (without the quotes) into the Selector Box. Then click publish and you should see the font in a few moments when reloading your blog. If it still doesn't work, try clearing your browsers cache (usually found in the preferences) and reload again.

Let me know if this helps,
Tej.

Is there full support for Chrome yet?

Does not work in Firefox 3.5.7

give me solution

http://img35.imageshack.us/img35/3420...

If Firefox is supported, why wouldn't Flock be? Flock is just Firefox with various "social" addenda...

What do you Typekit guys make of this - http://typophile.com/node/66568#comme... ?

See http://frdm.fr Good I think. Neat / Windows XP / Firefox 3.5.7 & IE 8 and Safari 4.0.4 & even Chrome 4.0.249.78. Thanks a lot to Typekit... (method : code in css).

When will you have support for Google's Chrome browser? I'm using Safari 4.0 on a Mac and Google's Chrome on Windows. Chrome is based on the same WebKit engine as Safari so I don't understand the incompatibility.

So I'm confused. You say your service does not support IE but this page shows your font in several IE environments: http://typekit.com/fonts/650

Browser support is a muddy subject that needs some major clarification.

Do you or do you not support IE?

I have a problem with the font Athelas.
My OS is Windows XP SP3.
The beautiful Italics of this font show correctly in Firefox, Safari, Chrome.
See :

But Internet Explorer 8 shows Athelas Regular, transformed in italics.
See :

Url of the text :
http://goo.gl/o7QB
François-R.