Side navigation
#9395 closed enhancement (wontfix)
Opened May 22, 2011 07:18PM UTC
Closed June 07, 2011 06:53PM UTC
Better Information About Events in Console
| Reported by: | giles.dermody@gmail.com | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | 1.7 |
| Component: | event | Version: | 1.6.1 |
| Keywords: | 1.7-discuss | Cc: | |
| Blocked by: | Blocking: |
Description
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""); });
Attachments (0)
Change History (14)
Changed May 22, 2011 07:27PM UTC by comment:1
| keywords: | → 1.7-discuss |
|---|
Changed May 22, 2011 08:31PM UTC by comment:2
| description: | 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""); }); → 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""); }); |
|---|
-1, Can be achieved with developer tools such as Firebug and Chrome
Changed May 23, 2011 01:06AM UTC by comment:3
-1, err...
Changed May 23, 2011 05:08AM UTC by comment:4
-1,
Changed May 23, 2011 11:15AM UTC by comment:5
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
Changed May 23, 2011 01:33PM UTC by comment:6
| description: | 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""); }); → 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""); }); |
|---|
"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
Changed May 23, 2011 01:33PM UTC by comment:7
| component: | unfiled → event |
|---|
Changed May 24, 2011 12:39AM UTC by comment:8
| priority: | undecided → low |
|---|---|
| status: | new → open |
Changed May 24, 2011 10:26PM UTC by comment:9
-1, Let's see it in a plugin first.
Changed June 03, 2011 02:11PM UTC by comment:10
| description: | 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""); }); → 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""); }); |
|---|
-1
Changed June 04, 2011 10:15PM UTC by comment:11
-1
Changed June 05, 2011 10:35PM UTC by comment:12
| description: | 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""); }); → 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""); }); |
|---|
-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.
Changed June 06, 2011 03:39PM UTC by comment:13
| description: | 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""); }); → 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""); }); |
|---|
-1
Changed June 07, 2011 06:53PM UTC by comment:14
| milestone: | 1.next → 1.7 |
|---|---|
| resolution: | → wontfix |
| status: | open → closed |
Closing per 1.7 roadmap meeting resolution
Nominating ticket for 1.7 discussion.