Okay, so the method above proved to work ok, once I made a special type to masquerade as a native browser event.
BUT- I think it works even better if treated as a special case from inside the MochiKit.Signal.connect() function itself. I've made a patch available, against the latest SVN, at http://nafpik.com/paul/mochikit-mouseenter.diff.html The patch wraps the listener function in Signal._observers with a suitable check when the user is trying to connect to mouseenter or mouseleave, and when the browser doesn't support that natively. I've tested it in FF/Windows, FF/Linux, Konqueror/Linux, IE6/Windows, and Opera/Windows (including the isChildNode function). Everything is happy. I'm new to the scene here- is it typical practice to provide diffs against the documentation as well when suggesting such a change? paul cannon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~----------~----~----~----~------~----~------~--~---
