Stuart Rackham
Thu, 05 Feb 2015 20:45:48 GMT
This is fixed on the latest release (2.0.8). Thanks!
The first example now "works" but it has XML (not HTML5) semantics i.e. the generated DOM no longer has HTML5 semantics. The cure is worse than the disease -- just drop the use of <foo/>-like XML style markup (I'm assuming that tags are HTML5, not some custom mix of XHTML and HTML5).