Weird problem with setTimeout() on Google Chrome
If you're getting the box immediately after dismissing the alert or confirmation, that's not odd, that's normal. confirm and alert completely stop JavaScript execution. The next call to the timer will queue up waiting for the interpreter to become available again, so dismissing the box bringing up the message doesn't surprise me. Is that the only behavior you're seeing that's a problem?