This article is in need of a technical review.
This article is in need of an editorial review.
insertAdjacentHTML() parses the specified text as HTML or XML and inserts the resulting nodes into the DOM tree at a specified position. It does not reparse the element it is being used on and thus it does not corrupt the existing elements inside the element. This, and avoiding the extra step of serialization make it much faster than direct
position is the position relative to the
element, and must be one of the following strings:
- Before the
- Just inside the
element, before its first child.
- Just inside the
element, after its last child.
- After the
text is the string to be parsed as HTML or XML and inserted into the tree.
Visualization of position names
<!-- beforebegin --> <p> <!-- afterbegin --> foo <!-- beforeend --> </p> <!-- afterend -->
afterendpositions work only if the node is in a tree and has an element parent.
// <div id="one">one</div> var d1 = document.getElementById('one'); d1.insertAdjacentHTML('afterend', '<div id="two">two</div>'); // At this point, the new structure is: // <div id="one">one</div><div id="two">two</div>
|DOM Parsing and Serialization
The definition of 'Element.insertAdjacentHTML()' in that specification.
|Feature||Chrome||Firefox (Gecko)||Internet Explorer||Opera||Safari (WebKit)|
|Basic support||1.0||8.0 (8.0)||4.0*||7.0||4.0 (527)|
|Feature||Android||Firefox Mobile (Gecko)||IE Phone||Opera Mobile||Safari Mobile|
|Basic support||?||8.0 (8.0)||?||?||?|
- on IE8, the changes to the dom are made only after the JS is finished, so if you need to access the generated nodes, it has to be in an asynchronous way.
- hacks.mozilla.org guest post by Henri Sivonen including benchmark showing that insertAdjacentHTML can be way faster in some cases.