W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2009

[whatwg] Exposing EventTarget to JavaScript

From: Ojan Vafai <ojan@chromium.org>
Date: Fri, 24 Apr 2009 19:36:22 -0700
Message-ID: <78dc8440904241936j6864c518t4885b436bea954e2@mail.gmail.com>
On Fri, Apr 24, 2009 at 7:26 PM, Boris Zbarsky <bzbarsky at mit.edu> wrote:

> Ojan Vafai wrote:
>>    If a linear list of things the event is targeting is sufficient, of
>>    course, and we're ok with the random third argument of
>>    addEventListener being carted around, then we might be ok using it...
>> I think this is sufficient. Although it is a bit unfortunate that dispatch
>> order is undefined.
> Those are unrelated issues, aren't they?  The linear list I was referring
> to is the proposed parentNode (or equivalent) chain; order there is
> well-defined, presumably.  For each element in this list, one can have
> multiple listeners for the event; the dispatch order here is currently
> undefined, but that could be changed.

Sorry, I had misread this.  Although, I think a linear list of things the
event is targeting is sufficient.

Is there a reason that they can't dispatch in a guaranteed order?
> You'd probably have to check with the folks who wrote DOM2 Events, if the
> question is why the spec says what it says.
> If the question is about current implementations, nothing obvious jumps out
> at me in the one implementation I'm familiar with (Gecko's).

Yeah, I'm more interested in implementation difficulties. I can't think of
anything obvious in WebKit's implementation either, but I'm not too familiar
with the event handling code.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090424/010267ad/attachment.htm>
Received on Friday, 24 April 2009 19:36:22 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:11 UTC