Reputation: 1998
Two questions:
How is the value returned from setInterval
and setTimeout
(the ones used to clear the timers) calculated?
Is it possible for both the functions to return the same value during runtime? For example:
var a = setInterval(fn1, 1000);
var b = setTimeout(fn2, 1000);
Is it possible for a
and b
to have the same value?
The first one is more of a for-my-knowledge question, but the second one is more important.
Upvotes: 43
Views: 65854
Reputation: 105
It sounds to me that the returned value is the index value for whatever internally maintained list of timers/intervals they are keeping.
As in point, I called clearInterval(18) instead of clearInterval(var_returned_from_set) and it stopped the desired timer/interval. (Tested FF17.0.1 and IE9.0.8)
Also in my own testing they appear to be unique for the lifetime of the page for both of those browsers.
Upvotes: 0
Reputation: 41381
Returns a value which can be used to cancel the timer. So, it would seem unlikely that they return the same value (unless they are reusing values and one of the timers has already been cancelled)
Mozilla states it's DOM level 0, but not part of the specification. (look at the bottom of the page)
I've got an even better reference:
Nabble says:
SetTimeout and setInterval are from the original Javascript specification, pre-ECMA. That specification is not officially standardized anywhere, but it is supported by all web browsers and most implementations of the Javascript language. (Including ActionScript.)
The pre-ECMA specs are often known as the "DOM-0" APIs. Since they have never been standardized before, it makes sense for HTML5 to finally spec the non-deprecated APIs in an attempt to provide a consistent environment across browsers. Especially when recent events have proven that there are companies who like to implement the letter of the standard, but not the spirit.
Read the original spec here, or from Sun (who was an early endorser of JavaScript).
Upvotes: 39
Reputation: 38005
Tested this under Opera 9, Safari 3, Firefox 3 and IE 7.
All returned integer values, starting at 1 and then incrementing by 1 for each call to setTimeOut()
and setInterval()
. However, I noticed that the browsers started the counters and handled them differently:
Notice though, that in all the scenarios, no two identifiers (at least in the same tab) are the same.
Upvotes: 36
Reputation: 5902
Whether they can have the same value depends on the JavaScript implementation. As Maciej mentioned in Firefox they can't have the same value as the same counter is used. However, that might be different in other browsers, so it is perhaps best not to rely on them never having the same value.
Upvotes: 2
Reputation: 3887
I think it’s not a standarized behavior. In firefox, it’s just integer, incrementing on each call of setTimeout
or setInterval
. And, no, they can’t have the same value.
Upvotes: 8
Reputation: 17794
From the Mozilla website:
intervalID is a unique interval ID you can pass to clearInterval().
So it is unique :)
Upvotes: 3