I would like to have a document fragment/element on the shelf to which I’ve connected a bunch of other elements. Then whenever I want to add one of these element-systems to the DOM, I copy the fragment, add the unique DOM ID and attach it.
So, for example:
var doc = document,
prototype = doc.createElement(), // or fragment
ra = doc.createElement("div"),
rp = doc.createElement("div"),
rp1 = doc.createElement("a"),
rp2 = doc.createElement("a"),
rp3 = doc.createElement("a");
ra.appendChild(rp);
rp.appendChild(rp1);
rp.appendChild(rp2);
rp.appendChild(rp3);
rp1.className = "rp1";
rp2.className = "rp2";
rp3.className = "rp3";
prototype.appendChild(ra);
This creates the prototype. Then I want to be able to copy the prototype, add an id, and attach. Like so:
var fr = doc.createDocumentFragment(),
to_use = prototype; // This step is illegal, but what I want!
// I want prototype to remain to be copied again.
to_use.id = "unique_id75";
fr.appendChild(to_use);
doc.getElementById("container").appendChild(fr);
I know it’s not legal as it stands. I’ve done fiddles and researched and so on, but it ain’t working. One SO post suggested el = doc.appendChild(el); returns el, but that didn’t get me far.
So… is it possible? Can you create an on-the-shelf element which can be reused? Or do you have to build the DOM structure you want to add from scratch each time?
Essentially I’m looking for a performance boost ‘cos I’m creating thousands of these suckers 🙂
Thanks.
Use
Node.cloneNode:Speed Tips
There are three operations you want to minimize:
String Parsing
This occurs when you use
innerHTML.innerHTMLis fast when you use it in isolation. It’s often faster than the equivalent manual-DOM construction because of the overhead of all those DOM method calls. However, you want to keepinnerHTMLout of inner loops and you don’t want to use it for appending.element.innerHTML += 'more html'in particular has catastrophic run-time behavior as the element’s contents get bigger and bigger. It also destroys any event or data binding because all those nodes are destroyed and recreated.So use
innerHTMLto create your “prototype” nodes for convenience, but for inner loops use DOM manipulation. To clone your prototypes, useprototype.cloneNode(true)which does not invoke the parser. (Be careful with id attributes in cloned prototypes–you need to make sure yourself that they are unique when you append them to the document!)Document tree modification (repeated
appendChildcalls)Every time you modify the document tree you might trigger a repaint of the document window and update the document DOM node relationships, which can be slow. Instead, batch your appends up into a
DocumentFragmentand append that to the document DOM only once.Node lookup
If you already have an in-memory prototype object and want to modify pieces of it, you will need to navigate the DOM to find and modify those pieces whether you use DOM traversal,
getElement*, orquerySelector*.Keep these searches out of your inner loops by keeping a reference to the nodes you want to modify when you create the prototype. Then whenever you want to clone a near-identical copy of the prototype, modify the nodes you have references to already and then clone the modified prototype.
Sample Template object
For the heck of it, here is a basic (and probably fast) template object illustrating the use of
cloneNodeand cached node references (reducing the use of string parsing and Node lookups).Supply it with a “prototype” node (or string) with class names and
data-attr="slotname attributename"attributes. The class names become “slots” for text-content replacement; the elements withdata-attrbecome slots for attribute name setting/replacement. You can then supply an object to therender()method with new values for the slots you have defined, and you will get back a clone of the node with the replacements done.Example usage is at the bottom.