I'm not sure this can be considered a bug, but I'm interested to see what happens with this for two reasons. It's related to my request for a single event object to be used all the time (which was determined not to be feasible) and it's delaying use of an event (which isn't fully supported - #7278).

Works for me.

One handler: http://jsfiddle.net/rwaldron/PsSNG/

Two handlers: http://jsfiddle.net/rwaldron/PsSNG/6/

@scott.gonzalez What about this: https://github.com/jquery/jquery/pull/301 ?

Just loaded 1.5.2 on my site and am still experiencing. I'll keep checking for Fiddle to update the versions to go there too.

The settimeout in my fiddle is simulating that I have local functions inside the one that grabs e. I don't need to reference e again until another click later on.

I don't understand why it's closed and working for you. The example in your fiddle is very different than mine. I can write another more complicated fiddle, without using setTimeout, that will show the error.

( Didn't mean to post as anon last time. Can't remember my login and forgot password isn't ending up in my mail. )

http://jsfiddle.net/davestein/q9Rjq/10/ Here is my fiddle that doesn't use setTimeout yet there is still an issue.

And as Scott points out the event is NOT being lost, just the property of data : http://jsfiddle.net/q9Rjq/9/

It's weird that everything stays but that becomes undefined.

Think about it this way: Events are just objects. If you pass the same object to several functions, any of those functions can modify properties on that object. If one of those functions happens to hold on to a reference to that object, that won't prevent other functions from modifying its properties. That's exactly what's happening here. There's nothing special about the data property. jQuery can potentially change it on every handler invocation. If you care about the data being "protected" you should put it in a closure and bind your event handler in the same closure.

Okay after digging through how everything is done in the jQuery source, I see how it's not a bug and impossible to do what I was suggesting.

Sorry for the trouble.

For accounting purposes I'm going to close this as invalid. It's not okay to use the Event object past an event handler's lifetime for reason #7278 among others.