Koen [XII]

Monkey patched the bug by adding ``` if (!view.afterFlushSet) { Tracker.afterFlush(callback); view.afterFlushSet = true; } ``` On line 63 in base.js, but have yet to find the cause of the...

Never mind, this causes other issues for the elements which were not problematic earlier...

Ok, what happens at the remove stage: 1. A new Nexus is added and thus the vm-bind-id is changed. List of Nexus.selectors: [vm-bind-id='250'] [vm-bind-id='282'] 1. The old Nexus should be...

Ok, I further pinpointed the issue: unbinding works as expected in our scenario, it is the binding however which gets executed twice and messes things up (probably for the same...

Would it help to know that these elements are rendered within a loop within a loop?

``` {{#each category}} {{#each products}} {{> productTemplate}} {{/each}} {{/each}} ``` Simplified representation (these are actually split over two templates).

Yes, but as I said it's a list of 30-something elements and there are times when elements 23 and 24 (for instance) are unaffected but the others are affected (which...

It's 30-something elements which all make use of the same template, most of the times all of them are affected but on rare occasions some of them are unaffected. So...

Following the code down the rabbit hole: For now I ended up at the bindHelper function of the viewModel which, apparently, gets called twice every time reconnect is called (for...

The order of events: # bindHelper ONE viewmodel.js:512 newNexus nexus.js:114 ===== nexus.js:103 onDestroyed nexus.js:300 unbind nexus.js:313 false