W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2014

[Bug 24403] WebIDL callbacks should probably default to pushing a new entry settings object

From: <bugzilla@jessica.w3.org>
Date: Mon, 27 Jan 2014 15:29:46 +0000
To: public-script-coord@w3.org
Message-ID: <bug-24403-3890-bw5OHvoaHm@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24403

--- Comment #4 from Bobby Holley (:bholley) <bobbyholley@gmail.com> ---
(In reply to Boris Zbarsky from comment #3)
> > step 3 of 'prepare to run a callback'
> 
> Nothing in event dispatch invokes that algorithm, as far as I can tell.  I
> realize the intent was to do so, but right now the spec just doesn't say to
> do it...

What about the part that says "In this step, invoke means to run the jump to a
code entry-point algorithm"?

> So if you do this:
> 
>   var objFromFrame1 = {};
>   objFromFrame1.handlEvent = funcFromFrame2;
>   foo.addEventListener("evt", objFromFrame1);
> 
> I'm pretty darned sure Gecko will treat frame1 as the entry settings object,
> not frame2.

Ok, but if you do:

foo.addEventListener("evt", funcFromFrame2)

I'm pretty sure Gecko will use frame2 as the entry settings object, even though
the implicit conversion to Function theoretically happens in the scope of
frame1.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 27 January 2014 15:29:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:51 UTC