Change VirtualTimePolicy::PAUSE_IF_NETWORK_FETCHES_PENDING

components/scheduler/renderer/renderer_scheduler_impl.cc

Index: components/scheduler/renderer/renderer_scheduler_impl.cc
diff --git a/components/scheduler/renderer/renderer_scheduler_impl.cc b/components/scheduler/renderer/renderer_scheduler_impl.cc
index 00a0426706bab6c32a24201a7c7061c3c84bf0a9..aec1ec24ce06d865118d16e27e7653316a94eaf0 100644
--- a/components/scheduler/renderer/renderer_scheduler_impl.cc
+++ b/components/scheduler/renderer/renderer_scheduler_impl.cc
@@ -1409,6 +1409,14 @@ void RendererSchedulerImpl::OnQueueingTimeForWindowEstimated(
                  queueing_time.InMillisecondsF());
 }
 
+void RendererSchedulerImpl::SetPerThreadTaskRunnerTimeDomain(

[Sami, 2016/07/28 10:46:34]

The next policy update can overwrite these settings. Should we instead make
virtual time be more of a global mode for the entire scheduler so it knows how
to set the appropriate time domains?

[alex clarke (OOO till 29th), 2016/07/29 13:35:01]

Done.

+    TimeDomain* time_domain) {
+  DefaultTaskRunner()->SetTimeDomain(time_domain);
+  CompositorTaskRunner()->SetTimeDomain(time_domain);
+  LoadingTaskRunner()->SetTimeDomain(time_domain);
+  TimerTaskRunner()->SetTimeDomain(time_domain);
+}
+
 // static
 const char* RendererSchedulerImpl::UseCaseToString(UseCase use_case) {
   switch (use_case) {