Deprecate $.fn.data("events") - Replace with debugging extension

[gnarf]

This was discussed when we talked about removing the .data("events") code. We would like to discourage/deprecate this usage, and perhaps release something like $.fn.events() to replace it in a "debugging extension".

I'd like to suggest that we deprecate the current usage as soon as possible.

[dcherman]

I use it for debugging, or at times for re-ordering already bound events if I need to bind something but have it fire first like this:

el.data( 'events' ).keydown.unshift( el.data( 'events' ).keydown.pop() );

[dcherman]

Thought I just had - what about maintaining a list of bound handlers on the element's event fn?

Something like el.keydown.getHandlers() returns [ function() { ... }, $.noop, somefunc ]

[dmethvin]

Given that I changed some of the internal structure of the events object during 1.7, several of the plugins that dig into the information in detail don't work properly anyway. I didn't realize this until we started the discussion yesterday and some people joined that thread. However, I have yet to be convinced that the people using "events" that way should be using them.

​https://github.com/jquery/jquery/commit/24e416dca36df4b182a612dba37f8b6cdaa25916

The data isn't being hidden, just moved to its rightful place in the internal data object so that user data named "events" won't clobber it. So we aren't preventing anyone from being able to inspect events for debugging purposes, which seems to be the most common need.

Once we come to a resolution on this and other 1.8 initiatives I'd suggest a blog post with the results so we can prepare people for the move from jQuery(elem, "events") to jQuery._data(elem, "events") with the warning that it is not a public interface and subject to change.

[jzaefferer]

+1

[jaubourg]

+1

[dmethvin]

+1, For access, let's stay with jQuery._data(elem, "events") so people understand it's not a documented interface.

[mikesherov]

+1