Bug Tracker

Opened 6 years ago

Closed 6 years ago

#9395 closed enhancement (wontfix)

Better Information About Events in Console

Reported by: giles.dermody@… Owned by:
Priority: low Milestone: 1.7
Component: event Version: 1.6.1
Keywords: 1.7-discuss Cc:
Blocked by: Blocking:

Description (last modified by scottgonzalez)

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.


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""); });

Change History (14)

comment:1 Changed 6 years ago by john

  • Keywords 1.7-discuss added

Nominating ticket for 1.7 discussion.

comment:2 Changed 6 years ago by rwaldron

  • Description modified (diff)

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

comment:3 Changed 6 years ago by jaubourg

-1, err...

comment:4 Changed 6 years ago by timmywil


comment:5 Changed 6 years ago by anonymous

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


comment:6 Changed 6 years ago by rwaldron

  • Description modified (diff)

"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."


comment:7 Changed 6 years ago by rwaldron

  • Component changed from unfiled to event

comment:8 Changed 6 years ago by timmywil

  • Priority changed from undecided to low
  • Status changed from new to open

comment:9 Changed 6 years ago by dmethvin

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

comment:10 Changed 6 years ago by john

  • Description modified (diff)


comment:11 Changed 6 years ago by addyosmani


comment:12 Changed 6 years ago by ajpiano

  • Description modified (diff)

-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.

comment:13 Changed 6 years ago by scottgonzalez

  • Description modified (diff)


comment:14 Changed 6 years ago by rwaldron

  • Milestone changed from 1.next to 1.7
  • Resolution set to wontfix
  • Status changed from open to closed

Closing per 1.7 roadmap meeting resolution

Note: See TracTickets for help on using tickets.