Fix for issue 198: User input should be saved after an "invalid XSRF token" error

Don't pay attention at app.yaml, the test server is live at http://60.retreview.appspot.com/2/

The fix is to have <textarea> field attached to every reply. Then browser can identify these <textarea>s and autofill them with saved values after going back from next page.

We do not output forms for every reply link, but generate forms dynamically. I assume it's done to save some space on page load. This fix moves <textarea> that is already available on the page for the given reply link into generated form.

The fix works in Chrome and doesn't work in FF5 Beta. FF5 seems to lose connection from original <textarea> to moved node. Mozilla bug opened: https://bugzilla.mozilla.org/show_bug.cgi?id=660549

[Andi Albrecht, 2011-05-31 20:41:34]

The idea is to have a textarea for each message instead of always cloning it?

I'm not sure how to test this change, but if it works for you I think we could
give it a try.

[techtonik, 2011-05-31 20:51:00]

To test it - just write reply to the message and then click any link on the page
without submitting. You will go to the next page. Hit back button and hit Reply
link again - you should get your previous message.

The idea here is that we lose <textarea> information, because when a page is
loaded after going back from the next page, there is no field to write the data
into. If <textarea> is there when a page is loaded, Chrome is able to correctly
write data into it. Hopefully, FF devs will make these changes too.

We can of course forget about page size and instead of cloning reply forms,
generate them for every message.

[Andi Albrecht, 2011-06-01 19:33:34]

LGTM

To me it looks a bit fragile how the JS works since it heavily relies on a
specific HTML structure. We just need to add (or remove) a single tag, maybe
even just a whitespace, to let things break. But this is of course not due to
your patch, that's just something we have to keep in mind :)

[techtonik, 2011-06-02 10:04:09]

Thanks. Committed in r756. I've increased version number to test this fix with
other browsers.

To make our app less fragile, we can switch to using selectors with Sizzle
library.