From 5a17a1ef1d77f0a99cb708adde283275b7eb49fd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Paul=20O=E2=80=99Shannessy?= Date: Fri, 11 Mar 2016 11:30:03 -0800 Subject: [PATCH] Update DOMLazyTree fragments comment to reflect reality --- src/renderers/dom/client/utils/DOMLazyTree.js | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/renderers/dom/client/utils/DOMLazyTree.js b/src/renderers/dom/client/utils/DOMLazyTree.js index 520a06c5f9..249eb475c5 100644 --- a/src/renderers/dom/client/utils/DOMLazyTree.js +++ b/src/renderers/dom/client/utils/DOMLazyTree.js @@ -53,9 +53,10 @@ function insertTreeChildren(tree) { var insertTreeBefore = createMicrosoftUnsafeLocalFunction( function(parentNode, tree, referenceNode) { - // Document Fragments in IE11, Edge (and possibly others) won't update - // correctly if they are already inserted. So we have to break out of our - // lazy approach and append children to the fragment before inserting it. + // DocumentFragments aren't actually part of the DOM after insertion so + // appending children won't update the DOM. We need to ensure the fragment + // is properly populated first, breaking out of our lazy approach for just + // this level. if (tree.node.nodeType === 11) { insertTreeChildren(tree); parentNode.insertBefore(tree.node, referenceNode);