Legacy block should be positioned with the respect to clearance

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

Index: third_party/WebKit/Source/core/layout/ng/ng_block_node.cc
diff --git a/third_party/WebKit/Source/core/layout/ng/ng_block_node.cc b/third_party/WebKit/Source/core/layout/ng/ng_block_node.cc
index 64f785b12f7dbd4f6205fdd8f32bba15cc331ad6..14c6097e3c96c2bf84bdb26e5977360ca3a6f2e4 100644
--- a/third_party/WebKit/Source/core/layout/ng/ng_block_node.cc
+++ b/third_party/WebKit/Source/core/layout/ng/ng_block_node.cc
@@ -264,7 +264,7 @@ DEFINE_TRACE(NGBlockNode) {
   NGLayoutInputNode::Trace(visitor);
 }
 
-bool NGBlockNode::CanUseNewLayout() {
+bool NGBlockNode::CanUseNewLayout() const {
   // [Multicol]: for the 1st phase of LayoutNG's multicol implementation we want
   // to utilize the existing ColumnBalancer class. That's why a multicol block
   // should be processed by Legacy Layout engine.