This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15120 - It would appear that setTimeout()'s algorithm doesn't ever actually check whether the task is still in the list of active timeouts, and doesn't remove the timeout from the list of active timeouts. Similarly with setInterval().
Summary: It would appear that setTimeout()'s algorithm doesn't ever actually check whe...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-08 22:46 UTC by contributor
Modified: 2012-07-26 07:21 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2011-12-08 22:46:10 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#timers
Complete: http://www.whatwg.org/c#timers

Comment:
It would appear that setTimeout()'s algorithm doesn't ever actually check
whether the task is still in the list of active timeouts, and doesn't remove
the timeout from the list of active timeouts. Similarly with setInterval().

Posted from: 2620:0:1000:147d:fa1e:dfff:fedd:ce8d by ian@hixie.ch
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.8 (KHTML, like Gecko) Chrome/17.0.942.0 Safari/535.8
Comment 1 Ian 'Hixie' Hickson 2012-01-31 22:46:11 UTC 
The check is in the task algorithm, it turns out. And setInterval() shouldn't clear it. But I added a note in setTimeout()'s algorithm about this.
Comment 2 contributor 2012-01-31 22:47:11 UTC 
Checked in as WHATWG revision r6955.
Check-in comment: Add a note about setTimeout() clearing the timer after running the task.
http://html5.org/tools/web-apps-tracker?from=6954&to=6955
Comment 3 contributor 2012-07-18 16:01:57 UTC 
This bug was cloned to create bug 18034 as part of operation convergence.