Preserving scroll position when changing path query

[johnthedebs]

Reopening this issue (previously: #337) since the changes don't seem to encompass this use case.

I'd like to preserve scroll position on a page when adding some query arguments to the URL but haven't figured out a way to do it.

If I set preserveScrollPosition for the page's route, it fixes the issue but causes the scroll position to be preserved coming from other pages as well. I also tried matching the query arguments in another Route, but was unable to match a ? literal.

Example code:

<Routes location="history">
    <Route name="index" path="/" handler={App}>
        <Route name="itemDetail" path="/items/:id/" handler={ItemDetail} />
        <Route name="itemGallery" path="/items/" handler={ItemGallery} />
        <DefaultRoute handler={Homepage} />
    </Route>
    <NotFoundRoute handler={Error404} />
</Routes>

When transitioning from /items/ to /items/?filter=blue the page scrolls back up to the top and there's no way to control the behavior.

[ryanflorence]

#439 seems related

[ryanflorence]

(total hack, but for now you can do some work in componentWillReceiveProps to mess with scroll position when a query shows up)

[gaearon]

If I set preserveScrollPosition for the page's route

There's no preserveScrollPosition anymore, the new setting is called ignoreScrollBehavior. Have you tried it?

it causes the scroll position to be preserved coming from other pages as well

That's precisely what ignoreScrollBehavior is intended to fix. Does this work?

<Routes location="history">
    <Route name="index" path="/" handler={App}>
        <Route name="itemDetail" path="/items/:id/" handler={ItemDetail} />
        <Route name="itemGallery" path="/items/" handler={ItemGallery} ignoreScrollBehavior />
        <DefaultRoute handler={Homepage} />
    </Route>
    <NotFoundRoute handler={Error404} />
</Routes>

(You'll need 0.9.x at least)

[johnthedebs]

I just tried ignoreScrollBehavior and it seems to accomplish what I was looking for. I'd gone over the documentation several times (after each update) and still managed to miss it somehow... Thanks for pointing it out!