Transitioned elements lose v-ref

[tim-smart]

See this codepen: http://codepen.io/anon/pen/ovcpq

[yyx990803]

Thanks for reporting - this is caused by a change to the transition implementation (components being transitioned out are destroyed after the transition finishes)

[tim-smart]

Interesting. In my app the state changes during the transition, so you can see things changing as the element transitions out.

Is there anyway to disconnect the data bindings before the transition starts?

[yyx990803]

The latest commit on next should have fixed that.

[tim-smart]

Much better, thanks!

However the event listeners still seem to be listening (registered through the events object on initiation)

[yyx990803]

Currently only directives are locked so no DOM updates will happen during the transition - events are expected to work until the component is destroyed. Are these event listeners breaking your logic for some reason?

[tim-smart]

I am using v-component="{{currentView}}" v-transition for routing, and once a route changes so does the data. Some events get fired when the data changes which leads to some inter-component communication that starts getting messy.

Removing v-transition makes everything work well haha. I'm just going to continue without transitions for now.

[yyx990803]

I reworked $destroy a bit more, it should now work like before, except destroyed will be called after the transition finishes (also after detached).

Let me know if this causes #488 to happen again...

[tim-smart]

Awesome, seems to be working great!