(CANCELED) [LayoutNG] Fix block child iteration in NGBlockLayoutAlgorithm::ComputeMinMaxContentSize

third_party/WebKit/Source/core/layout/ng/ng_block_layout_algorithm.cc

Index: third_party/WebKit/Source/core/layout/ng/ng_block_layout_algorithm.cc
diff --git a/third_party/WebKit/Source/core/layout/ng/ng_block_layout_algorithm.cc b/third_party/WebKit/Source/core/layout/ng/ng_block_layout_algorithm.cc
index 45688101a0bc7b59bddd1626c31a2c76ffd3e5ab..2c6538969bffe0780ef0450b468b2e171b9a625e 100644
--- a/third_party/WebKit/Source/core/layout/ng/ng_block_layout_algorithm.cc
+++ b/third_party/WebKit/Source/core/layout/ng/ng_block_layout_algorithm.cc
@@ -133,8 +133,9 @@ Optional<MinMaxContentSize> NGBlockLayoutAlgorithm::ComputeMinMaxContentSize()
     return sizes;
 
   // TODO: handle floats & orthogonal children.
-  for (NGLayoutInputNode node = Node().FirstChild(); node;
-       node = node.NextSibling()) {
+  NGBlockChildIterator child_iterator(Node().FirstChild(), nullptr);
+  for (NGLayoutInputNode node = child_iterator.NextChild().node; node;
+       node = child_iterator.NextChild().node) {
     MinMaxContentSize child_sizes;
     if (node.IsInline()) {
       // From |NGBlockLayoutAlgorithm| perspective, we can handle |NGInlineNode|