Re: Strict mode callbacks and setTimeout

On 7/8/11 5:10 PM, Mark S. Miller wrote:
>     There is only one task queue per task source for all Windows using the
>     same event loop. So window1 and window2 use the same task queue here.
> Cool. Then nothing breaks if we specify that a given setTimeout function
> uses the window from its birth environment, as if it was lexically
> captured?

That's unclear.  While there is only one task queue, the list of active 
timeouts is per-window.  And it's not clear what set of algorithms 
"started before this one" step 8 of 
refers to.  Just within a single event loop?  Or globally across the 
entire application?  Or something else?


Received on Friday, 8 July 2011 21:16:36 UTC