There is no way to disconnect connections created via NodeList.connect()

[mrblakwell]

if I connect an event to a bunch of nodes:

var foo = dojo.query(QUERY).connect("onchange",function(){/* .... */})

there is nothing in foo that allows me to disconnect these events. there are workarounds (see below) but nothing quick and easy.

from the #dojo IRC channel:

[14:56] mrblakwell: how do I disconnect events added via dojo.query(QUERY).connect("onchange",function(){do stuff})

[14:58] slightlyoff: mrblakwell: you don't =

[14:58] mrblakwell: sweet

[14:58] slightlyoff: mrblakwell: so I've been thinking about it

[14:58] slightlyoff: mrblakwell: and I keep thinking that connect could add a this.handles()

[14:59] slightlyoff: so you could get/keep a list of the handles that any connect() creates

[14:59] slightlyoff: which you'd then pass to something like NodeList?.disconnect(handles)

[15:00] slightlyoff: mrblakwell: if you file the bug I'll take it = )

following that, ptwobrussel suggested this as a workaround:

var handles =

dojo.query("a").map(function(x) {

return dojo.connect(x, "onclick",

function(evt) { /* ... */ });

});

/* Sometime later... */ dojo.forEach(handles, function(x) {

dojo.disconnect(x);

});

[bill]

Move all milestone 1.1 tickets to 1.2, except for reopened tickets and tickets opened after 1.1RC1 was released.

[bill]

defer dormant enhancements to "future" (they don't look like they're getting fixed soon so might as well mark as such)

[Chris Mitchell]

please review/triage

[dylan]

Is this relevant for dojo/on? Assigning to Kris to consider for 2.0.

[bill]

(I've been putting the NodeList tickets under the Query category IIRC)

[Kris Zyp]

Yes, this issue was solved with dojo/on.

[bill]

I don't get it, how does dojo/on solve this? (Also, if it's really fixed by dojo/on the milestone should be set to 1.7, to indicate that it was fixed in 1.7).

[bill]

Oh I see, NodeList.on() returns a list of handles, rather than a list of nodes.