Test distillability without JavaScript

third_party/WebKit/Source/core/dom/Document.cpp

Index: third_party/WebKit/Source/core/dom/Document.cpp
diff --git a/third_party/WebKit/Source/core/dom/Document.cpp b/third_party/WebKit/Source/core/dom/Document.cpp
index 61511cbb8f87521febca40cedfdf0fa6493108bd..cd466e6c00516f390a6e35adc50a1d65fe45108f 100644
--- a/third_party/WebKit/Source/core/dom/Document.cpp
+++ b/third_party/WebKit/Source/core/dom/Document.cpp
@@ -68,6 +68,7 @@
 #include "core/dom/DOMImplementation.h"
 #include "core/dom/DocumentFragment.h"
 #include "core/dom/DocumentLifecycleObserver.h"
+#include "core/dom/DocumentStatisticsCollector.h"
 #include "core/dom/DocumentType.h"
 #include "core/dom/Element.h"
 #include "core/dom/ElementDataCache.h"
@@ -1921,6 +1922,8 @@ void Document::layoutUpdated()
     if (isRenderingReady() && body() && !styleEngine().hasPendingSheets()) {
         if (!m_documentTiming.firstLayout())
             m_documentTiming.markFirstLayout();
+
+        m_statisticsCollector.collectStatistics(*this);
     }
 }
 
@@ -4584,6 +4587,8 @@ void Document::finishedParsing()
         InspectorInstrumentation::domContentLoadedEventFired(frame.get());
     }
 
+    m_statisticsCollector.setReadyToCollect();
+
     // Schedule dropping of the ElementDataCache. We keep it alive for a while after parsing finishes
     // so that dynamically inserted content can also benefit from sharing optimizations.
     // Note that we don't refresh the timer on cache access since that could lead to huge caches being kept