Larry Davis

@englishextra I think we're talking about two different things. Look at the code in the original issue, it passes `listener` to `gator.on()`, not the user-provided `callback`. As such, you cannot...

Dang, this project really needs tests. This particular PR would really benefit from a test that shows the problem and its fix.

@ccampbell sounds like a familiar struggle :) I reviewed a few PRs, filed some issues, and commented on a few things to get the conversation going again. I'll see what...

I'm afraid not, here's [a version of the Fiddle without regular listeners](http://jsfiddle.net/lazd/920fLt1d/2/). I updated the original Fiddle links in the issue body to be a little more clear.

Ah interesting. Yeah, the behavior is incorrect regardless, order should not matter in this scenario. It should be a quick fix, I just wanted to report it so it's tracked....

+1, Gator is a factory, not a constructor. After removing support for `new`, the `Gator` variable should be changed to `gator` so folks don't think it's a constructor.

In looking at this issue and @wesleytodd's PR #14 and working on another event delegation library, I realized there is actually a benefit to having multiple Gator instances per element......

@Zegnat, not quite, see [this fiddle](http://jsfiddle.net/lazd/9vhcuq7b/4/) for a simple constructor that implements the pattern I'm describing, let's call it the **Memoized Singleton with Override**. Basically, the input is "memoized" and...

@hawckins I edited the description to remove mention of RequireJS/AMD so this issue is only about types. Thanks!

There is discussion of solutions to the lack of `EXT_frag_depth` on this three.js issue: https://github.com/mrdoob/three.js/issues/13047