- commit
- b0c79fbfe3072f721b16ae01ef26753aa70f7819
- parent
- 695a69ce4ef982cf1ec819451bb566198379ba82
- Author
- Tobias Bengfort <tobias.bengfort@gmx.net>
- Date
- 2015-09-09 08:31
Fix updateDOM doc
Diffstat
| M | src/muu-update-dom.js | 10 | ++++++---- |
1 files changed, 6 insertions, 4 deletions
diff --git a/src/muu-update-dom.js b/src/muu-update-dom.js
@@ -6,17 +6,19 @@ 6 6 * 7 7 * The algorithms is relatively simple. It just iterates through all top level 8 8 * nodes. If a node has a different `nodeType` (e.g. text or element) or a9 -1 * different `nodeName` (e.g. div or ul) it is replaced completely and the10 -1 * algorithm proceeds with the node's children recursively. Otherwise, only11 -1 * the nodes's attributes are updated.-1 9 * different `nodeName` (e.g. div or ul) it is replaced completely. Otherwise, -1 10 * only the nodes's attributes are updated and the algorithm proceeds with the -1 11 * node's children recursively. 12 12 *13 -1 * Note that non-attribute properties (e.g. value) are lost in the first case-1 13 * Note that non-attribute properties (e.g. `value`) are lost in the first case 14 14 * and preserved in the second. 15 15 * 16 16 * If the algorithm encounters an element with the class `muu-isolate` it does 17 17 * not recurse into its children. This way, you can protect dynamically 18 18 * generated content from being overwritten. 19 19 * -1 20 * All classes prefixed with `muu-` will be preserved. -1 21 * 20 22 * @module muu-update-dom 21 23 * @param {Element} target 22 24 * @param {Element} source