Batched change notifies child component before parent stache binding

[dylanrtt]

This bug was introduced in 2.3 (absent in 2.2.9), and is still present in 2.3.15.

{{#eq page 'view'}}
  <foo-view page="{page}"></foo-view>
{{/eq}}

If <foo-view> binds to page, and page is changed in a batch, it seems the component is notified of the change before the stache binding. The stache binding should be called back first to remove the component and hopefully prevent the other batched event from running (however that works).

http://jsbin.com/xeqosawako/edit?html,js,console,output

[justinbmeyer]

There's an issue keeping this for 3.0. Essentially, live-binding relied on a synchronous notification of removed events to teardown the bindings.

In 3.0, for performance reasons, I was hoping to use MutationObservers to know when elements are added or removed. MutationObservers dispatch at the next turn.

I'm going to try to come up with a way for this to work without having to resort to synchronous "removed" events.

[justinbmeyer]

actually, listening to nodeLists teardown should work.

[justinbmeyer]

Issue moved to canjs/can-stache-bindings #278 via ZenHub