search for: currenttarget

Hello. I spent an hour or three chasing down a desired effect that mootools implements, namely the simulation of onmouseleave and onmouseenter events. Why? Lets say you have a Menu. A ul element that contains many li elements. If you want to have a function (maybe an effect) fire when the mouse moves outside of the ul, you are out of luck. Observe the mouseout function like so:

...}, element: function(event) { - var node = Event.extend(event).target; - return Element.extend(node.nodeType == Node.TEXT_NODE ? node.parentNode : node); + event = Event.extend(event); + + var node = event.target, + type = event.type, + currentTarget = event.currentTarget; + + if (currentTarget && currentTarget.tagName) { + // Firefox screws up the "click" event when moving between radio buttons + // via arrow keys. It also screws up the "load" and "error" events on images, + // re...

Note that one of the 8 patches (#6) will be sent separately in reply to this email, as some of the replaced lines are too long, so git won't let me send the email. However, there is nothing wrong with that patch, and it should be applied in the sequence listed below. Note also that I assume this will be tested on a clean f11 install, rather than an upgrade of an existing ovirt server