[Project_owners] Conflicting Event Listeners

Konstantin Svist fry.kun at gmail.com
Fri Jun 10 13:15:33 EDT 2005

I don't think there's a way to order them. Mind if I ask whay the two
extensions are doing that's conflicting?

As a SORT OF a workaround, you could try fudging with the third
parameter of addEventListener - that tells mozilla whether to capture
the event before or after it has reached the control where the event
is coming from. That's probably not a good idea in this case, though.


On 6/10/05, Scott Turner <srt19170 at gmail.com> wrote:
> On 6/9/05, Myk Melez <myk at melez.com> wrote:
> > Right.  Presumably the solution would be to use addEventListener() to
> > attach your event handler to the element, i.e. something like:
> > 
> > theElement.addEventListener("popupshowing", yourFunction, false);
> > 
>  Sorry, I guess my original posting wasn't clear.
>  This is what RIP and Platypus are doing (using addEventListener).  And all
> the addEventListeners should get executed (modulo somebody capturing the
> event, I guess).
>  The problem I'm having is the order in which the event listeners are being
> executed.  There's no way to tell whether RIP gets to go first or Platypus.

More information about the Project_owners mailing list