It supports the following DOM2 methods:
appendChild, cloneNode, hasAttributes, hasChildNodes, insertBefore, normalize, removeChild, replaceChild.
The following DOM2 properties are also supported:
attributes, childNodes, firstChild, lastChild, localName, namespaceURI, nextSibling, nodeName, nodeType, nodeValue, ownerDocument, parentNode, prefix, previousSibling, textContent.
Other methods can use documentFragment as a parameter (such as Node's appendChild and insertBefore methods), so fragment can be appended to the parent object.
Example：
var frag = ();
(('Ipsum Lorem'));
(frag);
() To put it bluntly, it is to save use of DOM. Every time JavaScript's operation on the DOM changes the page's monetization and refreshes the entire page, which consumes a lot of time. To solve this problem, you can create a document fragment, attach all new nodes to it, and then add the contents of the document fragment to the document at one time.
var oui=("oItem");
for(var i=0;i<10;i++)
{
var oli=("li");
(oli);
(("Item"+i));
}
The above code calls (oli) in the loop. Each time the browser executes this statement, the page will be updated. Secondly, the following () adds a text node and also needs to update the page. So the page needs to be updated 20 times in total.
In order to optimize the page, we should minimize the operation of DOM, add the list item after adding the text node, and use creatDocumentFragment() reasonably, the code is as follows:
var oui=("oItem");
var oFragment=();
for(var i=0;i<10;i++){
var oli=("li");
(("Item"+i));
(oli);
}
(oFragment);
W3C reference: http:///TR/DOM-Level-2-Core/#ID-B63ED1A3
-------------------------------------------
DocumentFragment is a "lightweight" or "minimal" Document object. It is very common to want to be able to extract a portion of a document's tree or to create a new fragment of a document. Imagine implementing a user command like cut or rearranging a document by moving fragments around. It is desirable to have an object which can hold such fragments and it is quite natural to use a Node for this purpose. While it is true that a Document object could fulfill this role, a Document object can potentially be a heavyweight object, depending on the underlying implementation. What is really needed for this is a very lightweight object. DocumentFragment is such an object.
Furthermore, various operations -- such as inserting nodes as children of another Node -- may take DocumentFragment objects as arguments; this results in all the child nodes of the DocumentFragment being moved to the child list of this node.
The children of a DocumentFragment node are zero or more nodes representing the tops of any sub-trees defining the structure of the document. DocumentFragment nodes do not need to be well-formed XML documents (although they do need to follow the rules imposed upon well-formed XML parsed entities, which can have multiple top nodes). For example, a DocumentFragment might have only one child and that child node could be a Text node. Such a structure model represents neither an HTML document nor a well-formed XML document.
When a DocumentFragment is inserted into a Document (or indeed any other Node that may take children) the children of the DocumentFragment and not the DocumentFragment itself are inserted into the Node. This makes the DocumentFragment very useful when the user wishes to create nodes that are siblings; the DocumentFragment acts as the parent of these nodes so that the user can use the standard methods from the Node interface, such as insertBefore and appendChild.
appendChild, cloneNode, hasAttributes, hasChildNodes, insertBefore, normalize, removeChild, replaceChild.
The following DOM2 properties are also supported:
attributes, childNodes, firstChild, lastChild, localName, namespaceURI, nextSibling, nodeName, nodeType, nodeValue, ownerDocument, parentNode, prefix, previousSibling, textContent.
Other methods can use documentFragment as a parameter (such as Node's appendChild and insertBefore methods), so fragment can be appended to the parent object.
Example：
Copy the codeThe code is as follows:
var frag = ();
(('Ipsum Lorem'));
(frag);
() To put it bluntly, it is to save use of DOM. Every time JavaScript's operation on the DOM changes the page's monetization and refreshes the entire page, which consumes a lot of time. To solve this problem, you can create a document fragment, attach all new nodes to it, and then add the contents of the document fragment to the document at one time.
Copy the codeThe code is as follows:
var oui=("oItem");
for(var i=0;i<10;i++)
{
var oli=("li");
(oli);
(("Item"+i));
}
The above code calls (oli) in the loop. Each time the browser executes this statement, the page will be updated. Secondly, the following () adds a text node and also needs to update the page. So the page needs to be updated 20 times in total.
In order to optimize the page, we should minimize the operation of DOM, add the list item after adding the text node, and use creatDocumentFragment() reasonably, the code is as follows:
Copy the codeThe code is as follows:
var oui=("oItem");
var oFragment=();
for(var i=0;i<10;i++){
var oli=("li");
(("Item"+i));
(oli);
}
(oFragment);
W3C reference: http:///TR/DOM-Level-2-Core/#ID-B63ED1A3
-------------------------------------------
DocumentFragment is a "lightweight" or "minimal" Document object. It is very common to want to be able to extract a portion of a document's tree or to create a new fragment of a document. Imagine implementing a user command like cut or rearranging a document by moving fragments around. It is desirable to have an object which can hold such fragments and it is quite natural to use a Node for this purpose. While it is true that a Document object could fulfill this role, a Document object can potentially be a heavyweight object, depending on the underlying implementation. What is really needed for this is a very lightweight object. DocumentFragment is such an object.
Furthermore, various operations -- such as inserting nodes as children of another Node -- may take DocumentFragment objects as arguments; this results in all the child nodes of the DocumentFragment being moved to the child list of this node.
The children of a DocumentFragment node are zero or more nodes representing the tops of any sub-trees defining the structure of the document. DocumentFragment nodes do not need to be well-formed XML documents (although they do need to follow the rules imposed upon well-formed XML parsed entities, which can have multiple top nodes). For example, a DocumentFragment might have only one child and that child node could be a Text node. Such a structure model represents neither an HTML document nor a well-formed XML document.
When a DocumentFragment is inserted into a Document (or indeed any other Node that may take children) the children of the DocumentFragment and not the DocumentFragment itself are inserted into the Node. This makes the DocumentFragment very useful when the user wishes to create nodes that are siblings; the DocumentFragment acts as the parent of these nodes so that the user can use the standard methods from the Node interface, such as insertBefore and appendChild.