Fwd: DOM Level 3 Events

2009/5/18 Boris Zbarsky <bzbarsky@mit.edu>

> I'm not sure what the ambiguity is.  The DOM3 Events drafy clearly says:
>
>  The target's ancestors are determined before the initial dispatch of
>  the event. If the target node is removed during the dispatching, or
>  a target's ancestor is added or removed, the event propagation will
>  always be based on the target node and the target's ancestors
>  determined before the dispatch. [1]
>
> DOM2 events has similar wording.
>
> What's ambiguous?


The paragraph isn't. It's just that it's not clear which object is intended
to be driving the event dispatch. It could be the Document object iterating
through the event targets or the event targets could pass the event to each
other in a chain. The second option would be feasible if the implementation
loads the event with the propagation path. I guess it's an implementation
detail but I was wondering if there was an "intended" way to do it...

Manu