# New page on router.push, old page on router.goBack

**URL:** https://forums.fusetools.com/t/new-page-on-router-push-old-page-on-router-goback/2009
**Category:** How-to Discussions
**Created:** [December 1, 2017, 4:15pm UTC](https://forums.fusetools.com/t/new-page-on-router-push-old-page-on-router-goback/2009 "2017-12-01T16:15:33Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Jacob\_H\_Rothschild](https://avatars.discourse-cdn.com/v4/letter/j/6f9a4e/32.png) [@Jacob\_H\_Rothschild](https://forums.fusetools.com/u/Jacob_H_Rothschild)
#### Post date: [December 1, 2017, 4:15pm UTC](https://forums.fusetools.com/t/new-page-on-router-push-old-page-on-router-goback/2009/1 "2017-12-01T16:15:33Z")

</div>

Hello, as we are building a large application, it is at times strongly preferred to completely remove and replace pages, instead of reusing them, having to reset all their state manually.

I have so far found ways to reuse all pages on `push` and `goBack`, and ways to replace all pages on `push` and `goBack`. What I have not found is a way to gain more control over when each of these happen. What I would like is to always get a new page on `router.push`, but always reuse the previous page on `router.goBack`.

How would I go about achieving this? Alternatively, how would I go about removing one or many/all pages, from JavaScript?

---

<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: [December 4, 2017, 12:35pm UTC](https://forums.fusetools.com/t/new-page-on-router-push-old-page-on-router-goback/2009/2 "2017-12-04T12:35:24Z")

</div>

Hi Jacob.

You could put a `Reuse="None"` on the page you `push` as suggested [in docs](https://www.fusetools.com/docs/fuse/controls/navigator/reuse). This, however, applies to a given page disregarding which direction you go to it.

Other than that, you need to take care of the state manually. If thought out well, it shouldn’t be too bad. Forcing a non-reuse on a lot of pages would have a significant impact on your apps’ performance, since a lot of new page instances would have to be created.
