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 16:34:06 +0000
To: public-script-coord@w3.org
Message-ID: <bug-24403-3890-DVhoIEvZsM@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24403

--- Comment #5 from Boris Zbarsky <bzbarsky@mit.edu> ---
> What about the part that says "In this step, invoke means to run the jump to a
> code entry-point algorithm"?

You mean in
http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#event-handler-attributes
?

That would apply to event _handlers_, but not to event _listeners_.

> I'm pretty sure Gecko will use frame2 as the entry settings object

Yes.  It will use the global of the actual object it was handed (which as I
said is possibly different from the object whose [[Call]] it will invoke).

> even though the implicit conversion to Function theoretically happens in the
> scope of frame1.

I don't see how Function is relevant here at all or what implicit conversion
you're talking about....  The model in the spec is that there is a WebIDL
callback object (in this case an EventListener) which is created with its
"callback context" set to frame1 in this case, because that's the incumbent
settings object when the API is called.  That "callback context" is then later
used to push an incumbent script settings object when the callback is invoked,
but of course that's not terribly observable from JS if the function is
scripted; you have to resort to some fun trickery to make it observable.

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

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