Have to run Typekit.load to actually load the typekit fonts

[alex88]

I use the loader like this:

WebFont.load({
  google: {
    families: [
      'Catamaran',
      'Droid serif',
      'Lato',
      'Merriweather',
      'Merriweather sans',
      'Open Sans',
      'Roboto',
      'Roboto Condensed',
      'Roboto Slab',
      'Titillium Web',
      'Source Sans Pro',
      'Montserrat'
    ]
  },
  typekit: {
    id: 'myid'
  }
});

and the js file is loaded, however the fonts are not, do I need to run Typekit.loadto actually load the fonts?

Since on the readme it seems it says that you have to use their embed code in case you don't have other fonts, but in this case I assumed it wasn't necessary as for the google fonts

[cmaion]

Bump!

New <typekit_id>.js code served by Typekit has changed.
Current webfontloader doesn't handle it.

In previous kits, window.Typekit.config.fn would return the list of fonts & variants. This is used by webfontloader's Typekit module to detect & load fonts.

In recent kits, the internal seems to have completely changed: the Typekit module doesn't do anything anymore, except loading the .js. Manually executing Typekit.load() does indeed load the fonts -- however, events handlers defined at webfontloader's level are not called.

Any chance the typekit module can/will be updated?
Or should we forget about using webfontloader to manage Typekit fonts?

Thanks!

[cmaion]

Actually, selecting a non-default charset results in a dynamic kit that is not supported here.
Keeping the defaults result in a kit that works.

[bramstein]

@cmaion We have two types of kits: dynamic and "regular". Most of our customers use regular kits, but if you're using a CJK font your kit will be converted to dynamic. Unfortunately, due to the way dynamic kits work, they're not compatible with the web font loader. We currently have no plans to support dynamic kits in the Web Font Loader.

[fluffgfx]

I'm having exactly the issue described here - The Typekit object is defined, but I have to run Typekit.load() to load the fonts on my page, which doesn't trigger any of the WebFont callbacks. I am not using CJK, my kit uses only the Default character set in two fonts with a single weight each (Proxima Nova Bold and Museo Slab 700, if it's any help.) Any idea why this would occur? Was my kit swapped to "dynamic" for some reason?

[gavmck]

+1 getting this issue here with default Proxima Nova on typekit

[b3rimbau]

@bramstein The fact that dynamic kits are not compatible with Web Font Loader and also don't trigger JavaScript font events in TypeKit's own embed code (the reason I was evaluating Web Font Loader) is a real problem when I need to recalculate layout (block height) dimensions after the web font has become active. Since TypeKit still manages to trigger the CSS events, it's not clear to me why it can't trigger the JavaScript events too.