zackbrown / famous-angular-ui-router Goto Github PK

Thanks for this btw, just looking how easy famo.us will be to integrate into existing architecture, in particular route changes.

Is it possible to use faAnimate with named nested uiView?

Like this: http://plnkr.co/edit/x7ITiRzusL6pDKsdMTRi?p=preview

In my case, I have an abstract state, which has a view called app, this state also modify other two internal views that compose it: header and content. And the children states also modify these views.

ui-view "app" abstract
     |
     ` --- ui-view "header"
     ` --- ui-view "content"
     |
 child state1
     |
     ` --- ui-view "header"
     ` --- ui-view "content"

I've been trying to figure out why or when, but basically the leaving surface is immediately set to opacity 0. The $done callback seems to execute right away (before the animation completes), which could be consistant with the operation for a Transitionable to execute on the first get?

I've tried preventing the $done callback from ever being called in my .leave and .enter functions but it doesn't seem to make any difference.

I'm new at famo.us so I'm clutching at straws here, but I'm happy to provide further investigation if guided.

Each time I navigate from main to test the content accumulates. It is not too noticeable at first, because they're all on top of each other, but if you add other content, or inspect the page you'll notice that new surfaces are being added each time, the existing ones are never removed?