modisposition

This is the content I've written so far in the official mjst repository . I'd love to know your thoughts about this little experiment, cheers! What mjst is a lightweight, about 1Kb minified and gzipped, and performances focused template engine with standards support. There are dozens JavaScript ? Template Engines solutions out there but as far as I know this is the only one based on validation for both client and server side programming languages. How There is one single function to call: // via text (e.g. Ajax or innerHTML from a template node) var transformed = mjst ( '<?js var hello = "mjst!"; ?><js-hello/>' ); // classic template node example < script id = "mytpl" type = "text/html" >   <? js     var hello = "mjst!" ;   ?>   < js - hello /> < /script> myEl.innerHTML = mjst(document.getElementById("mytpl")); / / via XML ( e . g . Ajax or a created document ) // this is a ...

This John Resig post about nodeName demonstrates once again how trustfulness are edge cases in JavaScript. I must agree 100% with @jdalton : frameworks or selector libraries should not be concerned about these cases. First of all there is no universal solution so whatever effort able to slow down libraries won't be perfect, then why bother? Secondly, I cannot even understand why on earth somebody could need to adopt XML nodes in that way. Agreed that importNode or adoptNode should not be that buggy, but at the same time I have always used XSL(T) to inject XML into HTML and I have never had problems. Different Worlds In an XML document a tag is just a tag. It does not matter which name we chose or which JavaScript event we attached, XML is simply a data protocol, or transporter, and nothing else. A link, a div, an head, the html node itself, does not mean anything different in XML so again: why do we need to import in that way? In Internet Explorer we have the xml property which i...