Hi, There is no order guarantee in either case (MDC doesn't discuss order [1], MSDN specifically says it's random[2]). You can determine empirically that IE does it one way and FF another, but you can't know that that won't change from dot release to dot release or even page to page.
If you need to guarantee the order of handlers, you'll need to attach a single handler and then have it register callbacks; have the handler call the callbacks in response to the event -- in an order you define. [1] https://developer.mozilla.org/en/DOM/element.addEventListener [2] http://msdn.microsoft.com/en-us/library/ms536343(VS.85).aspx -- T.J. Crowder tj / crowder software / com www.crowdersoftware.com On Sep 28, 11:45 pm, KammylandSoftware <kammyl...@gmail.com> wrote: > When ever you add oberservers to the same event such as > > Event.oberve("myElement", "mousedown", "someMethod_1()"); > Event.oberve("myElement", "mousedown", "someMethod_2()"); > > does IE execute them in REVERSE order upon fire? > > They get executed by order of chronological assignment in FF. > > IE is a bloody-idiot. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~----------~----~----~----~------~----~------~--~---