Better Information About Events in Console

[giles.dermody@…]

1) Make it possible to show what events are bound to a matched selector and the ORDER in which they will execute - maybe display this in JSON in the order they can be fetched 2) Make it possible to change the ordering of bound events on a matched selector.....somehow (-:

If 2) is impossible to do with a standalone function then it should be sufficient to unbind/rebind events manually if they were bound using namespaces in the first place - this is provided that solution 1) can be found and it is possible to query the current ordered events.

Example

Let's say a form plugin adds a function to a particular input element's ""change"" behavior..

...........(plug-in applies event to specified input).........

Then in the site script, the user wants to apply a couple of evenst manually to this form element. However, they want one event to occur before and one to occur after. This is only possible at the moment if:

1. $(""input"").change(function() { console.info(""manual event 1""); });
2. *run plugin*
3. $(""input"").change(function() { console.info(""manual event 3""); });

[john]

Nominating ticket for 1.7 discussion.

[Rick Waldron]

-1, Can be achieved with developer tools such as Firebug and Chrome

[jaubourg]

-1, err...

[timmywil]

-1,

[anonymous]

Can these be changed with developer tools though to do something like this?

​http://stackoverflow.com/questions/290254/how-to-order-events-bound-with-jquery

[Rick Waldron]

"Although all EventListeners on the EventTarget are guaranteed to be triggered by any event which is received by that EventTarget, no specification is made as to the order in which they will receive the event with regards to the other EventListeners on the EventTarget."

​http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-flow-basic-h3

[dmethvin]

-1, Let's see it in a plugin first.

[john]

-1

[addyosmani]

-1

[ajpiano]

-1, This DEFINITELY needs to be done in a plugin - it's a good idea for one (I took one pathetic crack at it once, and lost interest). It seems to have to be more of a "priority" system more than an "order" system, I tend to think.

[scottgonzalez]

-1

[Rick Waldron]

Closing per 1.7 roadmap meeting resolution