Type.js – remedying CSS’s typographic oversights

I can't imagine how a font acts across browser/OS differences is predictable enough to sanely/safely make decisions about kerning

Demo page:<p><a href="https://cdn.rawgit.com/nathanford/type.js/master/index.html" rel="nofollow">https:&#x2F;&#x2F;cdn.rawgit.com&#x2F;nathanford&#x2F;type.js&#x2F;master&#x2F;index.html</a>

Congrats on the work and more importantly about the idea!<p>Two things that I find ( in my opinion ) unpleasant :<p>1. Source code is hard to read ( some strange indentation and a lot of empty lines )<p>2. Support for dynamic content will do a lot of repaints.

This going to be huge for designers. Lack of proper kerning in CSS makes web fonts feel like half of a solution.

This should be using a -nathanford- vendor prefix for these library-specific CSS properties :&#x2F;.

Very cool :) Added some suggestions in the issues tab!

How is the performance on large bodies of text?