- From: <bugzilla@jessica.w3.org>
- Date: Wed, 10 Oct 2012 04:26:14 +0000
- To: public-webapps-bugzilla@w3.org
- Message-ID: <bug-19414-2532-L3RNbSjkjg@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19414 --- Comment #5 from Glenn Maynard <glenn@zewt.org> --- It's not a hack or a workaround at all; it's a common paradigm in every event-based system to queue tasks, and in the Web platform setTimeout is how you do it. If you want it to run as soon as possible when the current task completes, you set the timeout to 0. It's simple and clean, and it doesn't care whether you're running from an event handler, a timer, a generic callback, or anything else: it works everywhere consistently. I'll point out that what you're saying is a moving target: you started by saying that there's "guessing" and "presumption", and after explaining that there's no guesswork and that setTimeout is guaranteed to work, you started saying something else. Beyond that, I'm not spending more time on this ticket; I'll leave it to others. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 10 October 2012 04:26:15 UTC