dojo.event.browser.addListener creates closure

[guest]

While it's nice that dojo.event.browser.addListener attempts to fix the different event models for the various browsers, the creation of an anonymous function to perform this fix means that a later call to dojo.event.browser.removeListener with the same parameters will fail.

The documentation doesn't mention that addListener returns the anonymous function it creates. Nor does it mention the implications of the default value of the dontFix parameter -- that you'll be unable to remove the handler.

Most likely, the dontFix parameter should be changed to fixEvent where callers must deliberately request the creation of a closure.

[guest]

Test Case that demonstrates incorrect behaviour of dojo.event.addListener

[bill]

With the new architecture of 0.9 where disconnect() takes a handle (returned from connect) this is no longer an issue.