Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#14517 closed enhancement (fixed)

Scope normalization for Dojo/NodeList.connect

Reported by: webarnes Owned by: Kris Zyp
Priority: high Milestone: 1.7.2
Component: Events Version: 1.7.1
Keywords: Cc:
Blocked By: Blocking:

Description

The documentation (http://dojotoolkit.org/documentation/tutorials/1.6/events/) states that the scope for an event set using Dojo.connect is browser-dependent. It makes no claim about scope at all for NodeList?.connect (eg: Dojo.query('a').connect()), but I assume the same applies.

"Thankfully, Dojo normalizes the way you work with DOM events: it irons out the differences between DOM APIs and prevents memory leaks with one API: dojo.connect."

If the Dojo event manager is supposed to normalize events across browsers, it should also normalize the scope; preferably to the node that the event is connected to. To just say scope is browser dependent is a little weird. Having the scope bound to the node would be especially useful for NodeList?.connect, since you cannot solve the problem using closures (as the docs suggest for Dojo.connect).

Change History (2)

comment:1 Changed 7 years ago by Kris Zyp

Resolution: fixed
Status: newclosed

I believe this has been fixed in the tutorial trunk, and should be a part of the next push.

comment:2 Changed 7 years ago by bill

Milestone: tbd1.7.2
Note: See TracTickets for help on using tickets.