W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2011

Re: Strict mode callbacks and setTimeout

From: Mark S. Miller <erights@google.com>
Date: Fri, 8 Jul 2011 14:10:28 -0700
Message-ID: <CABHxS9iCBxBoySy_4cp4YeK5AuU3EHvbZQ2VRD4ee4Sr9v4itg@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: Allen Wirfs-Brock <allen@wirfs-brock.com>, Boris Zbarsky <bzbarsky@mit.edu>, Luke Hoban <lukeh@microsoft.com>, "es5-discuss@mozilla.org" <es5-discuss@mozilla.org>, public-script-coord@w3.org
On Fri, Jul 8, 2011 at 12:36 PM, Ian Hickson <ian@hixie.ch> wrote:

> On Thu, 7 Jul 2011, Mark S. Miller wrote:
> >
> > Exactly. It makes a difference. Should
> >
> >      window1.setTimeout.call(window2, ...)
> >
> > use window1's or window2's task queue?
>
> 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?
If so, can we go further and specify that setTimeout ignores its
this-binding?



>
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>



-- 
    Cheers,
    --MarkM
Received on Friday, 8 July 2011 21:10:56 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:04 UTC