# Animation in combination with Router

**URL:** <https://forums.fusetools.com/t/animation-in-combination-with-router/6670>\
**Category:** General\
**Created:** [January 11, 2018, 9:40pm UTC](https://forums.fusetools.com/t/animation-in-combination-with-router/6670 "2018-01-11T21:40:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jxns](https://avatars.discourse-cdn.com/v4/letter/j/d6d6ee/32.png) [@Jxns](https://forums.fusetools.com/u/Jxns)\
**Post date:** [January 11, 2018, 9:40pm UTC](https://forums.fusetools.com/t/animation-in-combination-with-router/6670/1 "2018-01-11T21:40:40Z")

</div>

I didn’t found something about this in the documentation so maybe you can help me here.

I have a Navigator-Structure:

```auto
<Navigator ux:Name="innerNavigation" Transition="None">
  <Page ux:Name="a" />
  <Page ux:Name="b" />
  <Page ux:Name="c" />
</Navigator>

```

All my Pages have an `ExitingAnimation` because I set `Transition` to `None`:

```auto
<ExitingAnimation>
  <Change Page.Opacity="0" />
</ExitingAnimation>

```

When I change my pages with `router.gotoRelative` and `router.pushRelative`, everything is working fine.  
But when I use `router.goBack` the `ExitingAnimation` is not getting called and the last page is placed behind the current (new) page.  
Why is the ExitingAnimation not working in this case?

---

<div class="post-metadata">

**Author:** ![Uldis](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/uldis/32/657_2.png) [@Uldis](https://forums.fusetools.com/u/Uldis)\
**Post date:** [January 12, 2018, 8:59am UTC](https://forums.fusetools.com/t/animation-in-combination-with-router/6670/2 "2018-01-12T08:59:33Z")

</div>

It all comes down to understanding what animation triggers are played, in what direction, when. See [this section in Navigation docs](https://www.fusetools.com/docs/navigation/navigation#custom-animations-transitions) for details. Here’s the important excerpt:

> The `Navigator` works with the standard navigation animation system in Fuse. This means that page transitions are defined by the following triggers:
> 
> - `EnteringAnimation` - played backwards for the entering page (the page becoming the active page)
> - `ExitingAnimation` - played forwards for pages replaced by a push
> - `RemovingAnimation` - played forwards for pages removed because of a goto
> 
> When you `goBack()`, the opposite happens:
> 
> - `EnteringAnimation` - played forwards for the page being removed by a `goBack`
> - `ExitingAnimation` - played backwards for the page being restored by a `goBack`