Koen [XII]

``` console.log(this.view) this.view[ViewModel.nexusesKey].remove(this); console.log(this.view) ``` Both view objects are identical and have identical contents (so no nexus is removed). Is it possible that the listener has changed, which is why...

I also noticed that the vm-bind-id of all elements changes every time after calling meteor.reconnect() (this also happens on elements where we do not experience the multiple bindings problem).

I tried downgrading to 0.9.4 indeed, the problem persisted.

Yeah, the thing is it only happens on one set of elements in our code, all other sets are unaffected, but I don't see anything in those elements which is...

wvanooijen92 is working on the same project... Don't know why he hasn't responded, he was also troubleshooting this. I checked: when adding a custom attribute the attribute remains (indicating the...

By the way: the vm-bind-id of ALL elements changes (not just those who depend on a GroundDB collection, also those who don't depend on a collection at all). And damn,...

Apologies for the inconenience :(

I just also tried switching back to jQuery (re-adding it as a dependency and using the .on and .off methods rather than the eventListener methods in plain Javascript but the...

Also I'm using Meteor 1.2.1

I can do you one better: the onInvalidate hook actually runs, the do_unbind value is true and it even ends up all the way at removeEventListener (with the (seemingly) correct...