This project is archived and is in readonly mode.

#902 ✓wontfix

Events in IE8 are fired out of order

Reported by ibolmo | May 7th, 2010 @ 06:01 PM | in 1.3.0 rc2 (closed)

Untested for < IE8. Modern browsers pass (Safari, FFx, and Chrome).

Comments and changes to this ticket

  • Jan Kassens

    Jan Kassens June 9th, 2010 @ 11:14 AM

    • State changed from “new” to “hold”

    We don't make any guarantee about the order in which events are fired. I'm not sure if there is a proper design that depends on the order of event listeners?

    We could fix this by only adding one native listener per element and event.

  • Fábio M. Costa

    Fábio M. Costa June 9th, 2010 @ 12:40 PM

    I'm afraid about the performance...

  • ibolmo

    ibolmo June 9th, 2010 @ 01:40 PM

    As I see it there's a couple of design choices.

    One: bind a single event per event that triggers the firing of events in the
    order specified when bound.

    Second: Unbind and rebind events in accordance to other browser behavior. I
    didn't test others but I think that FFx and Chrome are doing what is

    The first is a bit interesting, imo. 1 there's the idea that you're not
    binding multiple events to a single element but your relaying through
    mootools the firing of the event. E.g. you bind a mootools event trigger and
    when fired mootools has prior information to do something smart about that
    event. If we do this for all bound events we, or someone else, can do
    something cool with it. Since you could track the history of all fired
    events you can go back in time and say: user has been in box a and now moved
    to box b. Normally I'd only see mouseenter A, mouseleave A (plus other
    events), then mouseenter B. Maybe if we do this approach and give them a
    hooking mechanism that allows them to track if mouseleave A + mouseenter B
    then do something or fire a custom event.

    I also think that this could make bubbling up, user cancelling, and other
    stuff much more interesting. -

    Obviously, though, this is a bit complex. I'm just throwing ideas out there
    but option 2 is fair enough for IE.

  • Christoph Pojer

    Christoph Pojer November 9th, 2010 @ 07:25 PM

    • State changed from “hold” to “wontfix”
    • Milestone order changed from “0” to “0”

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Shared Ticket Bins

People watching this ticket