Browse limits are removed when returning to browse using the back button

[sarahjeansweeney]

When a user clicks on a result in a browse page limited by facets, returning to that page using the back button takes them to a fresh browse page, rather than the browse page with the limits they selected, which is not expected.

To replicate:

1. Visit the browse page for a CERES site (e.g. https://marathon.library.northeastern.edu/browse/)
2. Select any facet limits
3. Open one of the results
4. After the information page loads, click the back button to return to the browse page
5. The browse page will be missing the facets limits selected in step 2

Not sure if screenshots will help, but here are some:

Browse page with facets selected:

Clicked on the first record ("3D image processing..."), landed on the information page, then hit the back button. Was returned to the browse without the college facet applied to the browse list:

[patrickmj]

Can I ask for a confirmation across browsers, @sarahjeansweeney I'm seeing it in Chrome but not FF. You too?

[sarahjeansweeney]

I can see the issue in Chrome, but not in Firefox or Safari.

[patrickmj]

Thanks! Just makes the issue more interesting. Dunno if it's something about the back button behavior or how javascript works differently.

[patrickmj]

Looks like it's back button behavior. Here's the latest rabbit hole: https://stackoverflow.com/questions/31837195/chrome-vs-firefox-back-caching

https://forums.asp.net/t/1840836.aspx?+Different+behaviors+when+pressing+Back+Button+of+Browsers+IE+Chrome+Opera+

https://webkit.org/blog/427/webkit-page-cache-i-the-basics/

Weird that it's in Chrome and not Safari, since they're both WebKit if I remember right.