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:126.96.36.199) Gecko/20081029 Firefox/188.8.131.52
OS: Mac OS X → All
Hardware: x86 → All
Assignee: nobody → general
Product: Tamarin → Core
QA Contact: vm → general
Version: unspecified → Trunk
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
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 394769
You need to log in before you can comment on or make changes to this bug.