Crashes on Typekit-Homepage

funtoosh's Avatar


29 Oct, 2015 02:31 PM

Hey there,
This must be quite recent, I don't remember having had trouble with pages before. Trying to open pages like these crahes TFF for me:
Probably related to the issues with webfonts?

(TFF 38.3.0, Mac OS 10.5, G4 (7450) 1.25 GHz, 1 GB RAM)


  1. Support Staff 1 Posted by Cameron Kaiser on 30 Oct, 2015 12:46 AM

    Cameron Kaiser's Avatar

    Yes, this is another problematic webfont -- specifically "adobe-clean-han-japanese". However, Adobe is loading it by embedding it as data, not by referencing it as a URL. This is not merely an issue of loading it into the blacklist; I need to block these also and I don't have a mechanism yet. I won't be able to address this for 38.4, which is already being built.

    In the meantime, the issue is now tracked as issue 311:

  2. 2 Posted by Martin Niggeman... on 30 Oct, 2015 08:56 AM

    Martin Niggemann's Avatar

    Hi Cameron,

    thx for the quick reply!
    I don't fully understand the blacklist solution -- the blacklisted
    fonts are mostly fonts that don't even get displayed in the first
    place, aren't they?

    And yes, I guess the best way to block embedded base64 fonts would be
    via their names on CSS level.

    I noticed that at Typekit their CSS references the fonts like this:

    Which *should* mean the browser loads adobe-clean rather than the
    fallback adobe-clean-han-japanese, right?


  3. Support Staff 3 Posted by Cameron Kaiser on 31 Oct, 2015 12:50 AM

    Cameron Kaiser's Avatar

    Blacklisting a font is what we do when the font cannot be displayed by the operating system (10.4) and/or will make it crash (10.5). If we didn't blacklist it, it still wouldn't show, so yes, they're uniformly considered incompatible. Even Safari can't display them, but it uses a method of detecting them that is not compatible with 10.4, so we can't use it.

  4. 4 Posted by funtoosh on 04 Nov, 2015 01:56 PM

    funtoosh's Avatar

    I had a fresh look at typekit's code (this issue must really annoy me) and the way they set the font-family in their css is already weird, e.g.:

    [lang=ja_JP] [lang=de_DE] #hero-global-nav .wrapper h1 .arbeit 
    font-family:insert_at(flatten("effra"),"メイリオ","Meiryo","ヒラギノ角ゴ Pro W3","Hiragino Kaku Gothic Pro W3","Osaka","MS Pゴシック","MS PGothic",1)

    Never saw that before, nor could I find any CSS reference for an insert_at(flatten), let alone within font-family …

  5. 5 Posted by funtoosh on 09 Nov, 2015 12:26 PM

    funtoosh's Avatar

    Cameron, the problem has disappeared. No more crashes on Typekit's pages, and the weird syntax has also disappeared from their css .-)

  6. Support Staff 6 Posted by Cameron Kaiser on 11 Nov, 2015 10:01 PM

    Cameron Kaiser's Avatar

    No, the error is still present, at least on 10.4. The lack of a crash might just have been a lucky coincidence.

  7. 7 Posted by funtoosh on 12 Nov, 2015 09:55 AM

    funtoosh's Avatar

    Yep, I'm on 10.5 … and there's no more crashes with my configuration .-)

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac