This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html Section: http://www.whatwg.org/specs/web-apps/current-work/#timers Comment: setInterval should clamp to 4ms like setTimeout does, not 10ms Posted from: 71.184.125.56 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b13pre) Gecko/20110303 Firefox/4.0b13pre
Why?
Because there is no point to having them inconsistent: wages will just use setTimeout all the time. And because as far as I know every UA which lowered the clamp from 10ms lowered both timeouts and intervals.
Interesting. I'm pretty sure when I was speccing this that only the timeout clamp had been lowered in the UAs that lowered the clamp. I'll have to investigate closer.
https://bugzilla.mozilla.org/attachment.cgi?id=522433 seems to show me the 4ms clamp in Firefox current, IE9, Chrome current.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments.
Checked in as WHATWG revision r6362. Check-in comment: Make setInterval() clamp at 4ms as well. http://html5.org/tools/web-apps-tracker?from=6361&to=6362
mass-move component to LC1