Fix computation of runtime for throttled tasks

components/scheduler/base/time_domain.h

Index: components/scheduler/base/time_domain.h
diff --git a/components/scheduler/base/time_domain.h b/components/scheduler/base/time_domain.h
index fe1788c98cacec62f7e1da2c577c547f0f53c00a..d83c33d1fbca4f3581f9fa1fa062bbca8f62f592 100644
--- a/components/scheduler/base/time_domain.h
+++ b/components/scheduler/base/time_domain.h
@@ -49,6 +49,13 @@ class SCHEDULER_EXPORT TimeDomain {
   // Evaluate this TimeDomain's Now. Can be called from any thread.
   virtual base::TimeTicks Now() const = 0;
 
+  // Computes a runtime which is >= |time_domain_now| + |delay|. This is used to
+  // allow the TimeDomain to decide if the real or virtual time should be used
+  // when scomputing the task run time.

[Sami, 2016/02/23 11:41:22]

typo: computing

Could you add a note here saying this is thread safe?

[alex clarke (OOO till 29th), 2016/02/23 14:02:31]

Done.

+  virtual base::TimeTicks ComputeDelayedRunTime(
+      base::TimeTicks time_domain_now,
+      base::TimeDelta delay) const = 0;
+
   // Some TimeDomains support virtual time, this method tells us to advance time
   // if possible and return true if time was advanced.
   virtual bool MaybeAdvanceTime() = 0;