No longer clamp setTimeout(..., 0) to 1ms.

third_party/WebKit/Source/core/frame/DOMTimer.cpp

Index: third_party/WebKit/Source/core/frame/DOMTimer.cpp
diff --git a/third_party/WebKit/Source/core/frame/DOMTimer.cpp b/third_party/WebKit/Source/core/frame/DOMTimer.cpp
index 8a9ff9e0702187253872d79dfdd945c37b9820db..df9f2303d000d5a905829bf8c0c7dfa1ed8685c1 100644
--- a/third_party/WebKit/Source/core/frame/DOMTimer.cpp
+++ b/third_party/WebKit/Source/core/frame/DOMTimer.cpp
@@ -93,7 +93,7 @@ DOMTimer::DOMTimer(ExecutionContext* context,
   }
 
   double intervalMilliseconds =
-      std::max(oneMillisecond, interval * oneMillisecond);
+      std::max(singleShot ? 0.0 : oneMillisecond, interval * oneMillisecond);

[Sami, 2017/03/08 14:15:55]

Did we try to make the minimum always be 0 for all types of timers? That's what
the spec calls for I think. Maybe add a TODO for that here?

   if (intervalMilliseconds < minimumInterval &&
       m_nestingLevel >= maxTimerNestingLevel)
     intervalMilliseconds = minimumInterval;