Thanks for the report! Could you create a minimal example on
http://jsbin.com?

Michał Gołębiowski

Example here: http://jsbin.com/padibumefo/1/edit?html,console,output

There seem to be two documented properties that are not copied, detail and prevValue. I have no idea why prevValue is listed there and I removed it.

Because of the overhead of copying properties, I'm hesitant to add detail and as you say it's available through originalEvent. So we can either update the docs to remove it (my preferred route) or add it. Note that adding it won't help anyone until the next release anyway so the docs wouldn't be correct as-is unless we put in some note like "this was added in jQuery 3.0".

I had this same problem recently in a project, where I initially assumed the property was present.

After some thought I realized jQuery already have a custom way to handle this using the data property.
Since the detail property is a standard way to pass data to the triggered callback without using jQuery, it makes sense to be available in the original event.

In other hand, the callback is not portable between native and jQuery-based environments.
Is portability something to be considered in this case when dealing with an event triggered by a third party that doesn't use jQuery?

Any property not normalized by jQuery can be accessed via originalEvent, and there are plenty of special ones that are only used by one or two events. The copying to jQuery's event is something we want to keep to a minimum since it has real costs and is in a time-critical section of code. Accessing the value through orginalEvent doesn't cause any problem, does it?

As I mentioned, in my case in particular the only problem was the code portability.

When I ported the event handling callback from another codebase I initially expected it would work without changes in a jQuery environment using the ui widget factory. What happened instead is that I had to change event.detail to event.originalEvent.detail.

It is not a big deal though if performance is an issue. Updating the docs seems reasonable.

Per discussion in the meeting today, let's add .detail to match the current docs.

Any chance to get this fix in the stable branches?

Is there a problem using event.originalEvent.detail instead?

Not really - just have to make sure we always use jquery for attaching events.