I am aware I could batch all of my font requests together into one call with webfontloader to sidestep this problem (e.g. families: ['Lato', 'Oswald']). However, due to the nature of our web app, this is not a good solution -- we have multiple components requesting their own fonts.
When attempting to use webfontloader two times, one of the requests fails its active callback:
http://codepen.io/jedierikb/pen/JRbxXK
I am aware I could batch all of my font requests together into one call with webfontloader to sidestep this problem (e.g.
families: ['Lato', 'Oswald']
). However, due to the nature of our web app, this is not a good solution -- we have multiple components requesting their own fonts.(this bug is a better explanation of the issue first described https://github.com/typekit/webfontloader/issues/344)