I don't really understand your question (maybe because of my english, sorry), but I take advantage of your post to show my comment here : http://trac.mochikit.com/ticket/27.
To make it clear, I don't think modifying the event object is a good thing, and is totally against MochiKit usual code. I'd prefer multiple methods that does what I want (pointerX(event) for example, or pointers(event) if you want to get X et Y at the same time) over your big single _fixEvent where 80% of the job is useless in 80% of the time. The other problem is see is the stop of events by default (it's really lame, you can't even access the shortcuts of your browser after), and __listeners/__signals slots added to objects (that would be great to do without, and I think there's solution). Besides, you're doing a great job in compatibility, and I hope it will be integrated one way or another. -- Thomas
