Bug 67501 - set DOMTimer's default min timeout from 10ms to 4ms as per w3 WG
Summary: set DOMTimer's default min timeout from 10ms to 4ms as per w3 WG
Status: RESOLVED DUPLICATE of bug 61214
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-02 10:33 PDT by Srikumar B
Modified: 2011-09-02 22:18 PDT (History)
1 user (show)

See Also:

Attachments
Patch to change the default timeout value (1.29 KB, patch)
2011-09-02 11:15 PDT, Srikumar B 		ap: review-
ap: commit-queue-
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Srikumar B 2011-09-02 10:33:25 PDT 
As per the W3 working group standard http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html#timers, the default timeout for setTimeout() , setInterval() should be 4ms in DOMTimer but it is currently set to 10ms (s_minDefaultTimerInterval)
Comment 1 Srikumar B 2011-09-02 11:15:24 PDT 
Created attachment 106163 [details]
Patch to change the default timeout value

DOMTimer default value changed from 10ms to 4ms as per the w3 WG http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html#timers

As the value is a minimum timeout, i think there is no straight forward way to test this case. I made sure all the existing DOMTimer tests are passing.
Comment 2 Alexey Proskuryakov 2011-09-02 22:18:43 PDT 
Comment on attachment 106163 [details]
Patch to change the default timeout value

It was intentionally left for ports to decide when/if they want to change the minimum interval. Grepping sources, it appears that not all ports chose to change it, so it may not appropriate to change the default at this time.

Also, duping to an existing bug.
Comment 3 Alexey Proskuryakov 2011-09-02 22:18:56 PDT 

*** This bug has been marked as a duplicate of bug 61214 ***