Sapper doesn't render pages which are set by pushstate

[antony]

A little background - pushstate is used a lot when persisting a page which results from a search query. Adding parameters dynamically and then allowing the user to click back in order to return to their filtered search results.

It appears that doing so in Sapper doesn't work - the title changes, and the URL changes in the browser, but hitting back doesn't re-render the page, unless you then navigate forward again and then backwards.

I've created a reproduction here: https://github.com/antony/sapper-pushstate-issue

[antony]

A little bit of digging around the sapper source code by @pngwn and I found that there is some pushstate data { id: cid } added to Sapper's own pushstates. Naively adding { id: 0 } to my pushstate call makes pushstate work predictably.

I suppose the question for @Rich-Harris or @Conduitry is - what is cid, and is it dangerous to make it up randomly...

[PatrickG]

Instead of using pushState directly, you could use the goto function from @sapper/app.
Sadly there is no way (yet?) to add properties to the state.

[antony]

@PatrickG goto sadly won't work for me as it actually changes the page. I just want to inject state into the URL so that when people hit back from a search result, the application returns to a page with search filters, and so that people can share a page of search results.