Alex, yes, I realized this and more when I discovered:
- Line 231 in can/view/live.js (v2.0.4) handles the removal of {{#each}} elements.
- Line 178 in can/view/elements.js (v2.0.4) handles the removal of {{#if}} elements and possibly others.
Getting an event or other in there would involve extending the above mentioned files; something that some of them were not designed for. Much duplication would be involved, thereby rendering them un-future-proof. Perhaps they'll accept a Github pull request to correct this. I am also considering simply extending can.remove.
Moreover, once written, it should handle all removals and no longer necessitate both can.Transition.Map and can.Transition.List. For cases where error is true, then false, then true again, two transitioning elements will temporarily be displayed; and I think that is visually correct logic.