The only (unreasonable) solution is to persist the data in some way so your
models can pull the updated data.
If it is temporary (i.e. not permanent cross sessions), then storing the
page data in the session will work. If it is more permanently tied to the
user, you can probably store it in the
Hi Sven,
I only actually need 1 level of 'back'
I thought of two (far fetched?) things:
1. Have an unbeforeunload trigger some ajax request that might store the
state and return some id that could be stored in the window.history and
detect the back, retrieve the id, and instantiate a new page
Hi Rob,
without a redirect, your first page will be presented without page id in
the url.
Thus when you return back from another page, the browser will just
request a fresh page. An F5 while on your first page should result in
the same problem.
I don't know how to square that circle.
Hi all,
We switched our app to use the renderstategy ONE_PASS_RENDER for SEO
reasons (reduce the number of redirects).
However, this causes the back-button to behave differently.
Before, when we update a part of the screen via ajax; then following a
link, then going back shows the page as it
