Improved Typekit embed code

typekit.js

(function(d) {
  var tkTimeout=3000;
  if(window.sessionStorage){if(sessionStorage.getItem('useTypekit')==='false'){tkTimeout=0;}}
  var config = {
    kitId: 'a1b2c3f4',
    scriptTimeout: tkTimeout
  },
  h=d.documentElement,t=setTimeout(function(){h.className=h.className.replace(/\bwf-loading\b/g,"")+" wf-inactive";if(window.sessionStorage){sessionStorage.setItem("useTypekit","false")}},config.scriptTimeout),tk=d.createElement("script"),f=false,s=d.getElementsByTagName("script")[0],a;h.className+=" wf-loading";tk.src='//use.typekit.net/'+config.kitId+'.js';tk.async=true;tk.onload=tk.onreadystatechange=function(){a=this.readyState;if(f||a&&a!="complete"&&a!="loaded")return;f=true;clearTimeout(t);try{Typekit.load(config)}catch(e){}};s.parentNode.insertBefore(tk,s)
})(document);

Small note, just as an FYI for anyone who doesn't know. The default embed code has it's own prescriptive JS for how FOUT should be handled.

That code looks like this (at the time of this writing):

    <script type="text/javascript" src="//use.typekit.net/yourKitID.js"></script> <!-- e.g. "a3b0btq.js" -->
    <script type="text/javascript">try{Typekit.load();}catch(e){}</script>

Your code is helpful for anyone who wants to take control of how font loading happens on their website, but since Typekit has so much happening behind the scenes, I prefer to use their "default" code because if they change something about how fonts are loaded, it should automatically be updated and not become out of sync, whereas your code is more likely to be affected by some kind of internal organization-level deprecation.

Is this script still working?

@renatocarvalho We're still using it on our sites with no problems since we created it.

works great for me! awesome work @skddc

Still working, thanks for the fix!