setTimeout and setInterval seem to pass an int to their function when not given any arguments to pass. Worse still, the value changes randomly. Usually it's 0 or -1, but I've seen many other negative numbers.

Sit and watch the testcase, and you'll see it intermittently change from green to red and back again.

Confirmed on Linux m-c trunk, as well as in Firefox 2. :) Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20090820 Minefield/3.7a1pre Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.18) Gecko/20081029 Firefox/2.0.0.18

Old Netscape extension, it's the "lateness" of the timeout. From Netscape 3 or 4. Time to lose it. /be

I'll mention bug 394769 here as Gavin added a number of CCs who may be interested. Traditionally this has been bug 10637

I suggest duping this to bug 394769 and confirming that bug; we can let bug 10637 stand for its day when it was indeed WONTFIX. Thanks for finding these bugs. /be

Should that bug be moved to JavaScript Engine, Brendan?

(In reply to comment #8) > Should that bug be moved to JavaScript Engine, Brendan? No, setTimeout and related APIs are DOM APIs, the JS engine doesn't have anything to do with them (other than running the timeout, of course!).