Koen [XII]

Just the one I read on my phone (currently doing research for my thesis, so have to multitask a little). I guess that makes sense (not calling a second bind...

It seems unbind is called before bind is called, re-checking at the point in time where the removeEventListener and addEventListener are actually called.

Ok, what happens for one specific element: 1. bind is called 2. unbind is called (the element, at this point, already has a new vm-bind-id) 3. bind is called again...

The guid of the listener in the 1st bind function is the same as the guid of the listener in the unbind function though...

I collected the Nexuses at 1 (bind called), 2 (unbind) and 3 (bind called again). (Right before addEventListener and removeEventListener.) http://imgur.com/iEvmTW7 Is there anything you would like me to take...

Ok, as I mentioned earlier I re-implemented jQuery in your latest version (just api.use('jquery') and added on and off instead of addEventListener and removeEventListener. What I did now was remove...

Strange things are happening... When I call $(elem).off() (wihout type and listener) the bind event does not get fired a second time. The result is obviously that the button no...

Ok, using jQuery I was able to find out that the listeners actually do get removed (when I console.log jQuery._data(elem, "events") right after the .off call there are not click...

Looking at the amout of Nexuses listed in the global list I don't think there are duplicates, but there are multiple Nexuses attached to a single element, that's for sure....

As far as I have been able to tell unbind is just triggered once, I'm looking at bind now.