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

--- Comment #3 from Boris Zbarsky <bzbarsky@mit.edu> ---
> 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...

> It remains to be seen whether this is web compatible, though.

Hmm.  I guess Firefox 27 is the first Gecko release that actually guarantees
the behavior you describe.  So far we haven't had any issues reported on it,
but of course we haven't released it yet.

> both use the global of the function getting called (I think)

I don't think Gecko does at the moment.  Gecko uses the global of the JS object
that implements the callback or callback interface.

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.

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

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