rails/turbolinks — pull request #332 by antpaw (2014-01-24 15:14:20+00:00)
Title: Forms behave wrong on history back

The Problem right now is that `window.addEventListener 'popstate'` fires immediately after it is set, I don't see a reason for this to happen. Most of the time you don't notice it, the same page gets loaded twice (second time from cache), (that's bad, because some unnecessary code gets executed), but the user doesn't notice it. While working with forms its different, when the user submits a form and goes back in browser history, he should see the stuff he entered/changed in the form, instead Turbolikes loads the inital page from cache and replaces it. User sees the form like he found it when he was starting to work on it. In some cases this is more then a terrible user experience. Please please explain me why this stuff needs to happen or fix it :)