Creating normalized fragments

There is a method I've never used that *might* speed things up
in terms of tree walking, and improve, in general, layout
expectations.

This branch is here to test that's the case.

cjs/node.js

@@ -34,9 +34,9 @@ const isImportNodeLengthWrong = importNode.length != 1;
 // later on, so that paths are retrieved from one already parsed,
 // hence without missing child nodes once re-cloned.
 const createFragment = isImportNodeLengthWrong ?
-  (text, type) => importNode.call(
+  (text, type, normalize) => importNode.call(
     document,
-    createContent(text, type),
+    createContent(text, type, normalize),
     true
   ) :
   createContent;

cjs/rabbit.js

@@ -54,7 +54,7 @@ const createEntry = (type, template) => {
 // operation based on the same template, i.e. data => html`<p>${data}</p>`
 const mapTemplate = (type, template) => {
   const text = instrument(template, prefix, type === 'svg');
-  const content = createFragment(text, type);
+  const content = createFragment(text, type, true);
   // once instrumented and reproduced as fragment, it's crawled
   // to find out where each update is in the fragment tree
   const tw = createWalker(content);