Note that there are some explanatory texts on larger screens.

plurals
  1. POEmber.js routing, outlets and animation
    primarykey
    data
    text
    <p>It seems like if you want to animate a transition between states using the new Ember.js router and outlets, you're out of luck, since the previous content of an outlet will be destroyed before you have a chance to animate it. In cases where you can completely animate one view out before transitioning to the new state, there's no problem. It's only the case where both old and new views need to be visible that's problematic.</p> <p>It looks like some of the functionality needed to animate both the previous outlet content and the new was added in <a href="https://github.com/emberjs/ember.js/pull/1198" rel="nofollow noreferrer">this commit</a>, but I'm not sure I understand how to use it.</p> <p>There's also been some discussion about using extra transitional routes/states to explicitly model the "in-between" states that animations can represent (<a href="https://github.com/emberjs/ember.js/issues/779" rel="nofollow noreferrer">here</a> and <a href="https://github.com/emberjs/ember.js/commit/b5ff0edb41f50e1f55446c14605fb566aa419ed4" rel="nofollow noreferrer">here</a>), but I'm not sure if it's currently possible to match this approach up with outletted controllers and views.</p> <p>This is similar to <a href="https://stackoverflow.com/questions/11083392/ember-js-routing-how-not-to-destroy-view-when-exiting-a-route?rq=1">How *not* to destroy View when exiting a route in Ember.js</a>, but I'm not sure overriding the <code>outlet</code> helper is a good solution.</p> <p>Any ideas?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload