The way I see it, the event triggers the proper listener, the one in the
document. If there was a listener in the layer, that would fire first and would
have the possibility to cancel bubbling.
The target property is mainly used in order to 'attach' an object to the event
inside the listener, as it is needed inside widgets. In your example if you want
to know were did the event initially occur, you could get it from the event's
src property.
e.getSource()
Always speaking theorically
Brandon Myers wrote:
> Yes.. This is proper DynAPI event behavior.
> The browser, especaily NS, will trigger the document as well as the layer.
>
> ----- Original Message -----
> From: "Pascal Bestebroer" <pa...@dy...>
> To: "Dev" <dyn...@li...>
> Sent: Saturday, December 02, 2000 5:56 AM
> Subject: [Dynapi-Dev] events
>
> > I've been playing with events, and I'm a bit out of the loop here.
> >
> > I have this setup:
> >
> > a dynlayer on a document.
> > an eventlistener that has the document as a target
> > the eventlistener is attached to the document.
> >
> > When I click the layer, the event is triggered on the document.. this
> > shouldn't be correct should it? I'm not sure if this behaviour has always
> > been this way, but it just doesn't seem right.
> >
> > any thoughts?
> >
> > Pascal Bestebroer
> > pa...@dy...
> > http://www.dynamic-core.net
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
|
