suggest this is migrated to stackoverflow - it's not really a WP issue.
–
anuAug 15 '12 at 15:02

1

It IS because I know how to do typekit in the general case. What I'm trying to do is put it into the WordPress editor. If it's moved over to Stack Overflow there'll just be a load of people going "hmmm but this is a WordPress question =s"
–
Tom J Nowell♦Aug 15 '12 at 15:03

3 Answers
3

Tom Nowell's TinyMCE plugin solution works brilliantly, just update the JavaScript to use Typekit's new async code. Once you use the new async embed code, the 403 problem disappears and you'll have Typekit-enabled TinyMCE with no fuss!

Tom has put all the code together in a blog post. He did all the heavy lifting on this, so go give him some pageviews and read the specifics there!

It does? ( I both asked and answered =p ) my solution would work if it weren't for the security, if I could set the src of the iframe to a blank page on the same domain it would work, I shall test the new async code though!
–
Tom J Nowell♦Sep 10 '12 at 9:09

Isn't as simple as that, it's inline script, but if adding it in the admin is enough for the css to pick it up then it should work =]
–
Tom J Nowell♦Jul 25 '12 at 16:44

This doesn't actually work. Aside from a missing semicolon and a closing bracket, once fixed it adds the font to the post edit screen, I can change the WordPress UI, but I cannot use the font in the editor styles. My post content refuses to use the typekit fonts and instead displays in whatever the next fallback fonts are available.
–
Tom J Nowell♦Aug 15 '12 at 11:25

The JS itself it would appear needs inserting into the iframe tinyMCE uses, not the parent frame that loads the WordPress post UI
–
Tom J Nowell♦Aug 15 '12 at 11:25

I was able to fix the problem of the CSS file being forbidden by copying the css into my editor-style.css. Its a super hackish fix but it worked, after I had tried just about everything else.
–
ColeSep 22 '12 at 3:54