Setting the timeout to 0ms is misleading at best, and ambiguous at worst. For one, it suggests that the timer will execute synchronously or at least in the current event loop, but in fact it executes asynchronously. The resolution of timers in most browsers is about 10ms, so setting the timeout to 0 or 1 is irrelevant, it still executes after 10ms at the earliest.
Also, its slightly cheaper to use Scheduler#scheduleDeferred for one off timers. Scheduler creates one native timer and fires all deferred commands from a queue. That's more efficient than creating one native timer per command. If other people really want this change, feel free to convince me otherwise. http://gwt-code-reviews.appspot.com/1506802/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
