3 ms·
I take it you know that the continuation timeout problem affects replies as well? Because I think it sucks that when I spend more than a few minutes composing
by gizmo 18y ago
I take it you know that the continuation timeout problem affects replies as well?
Because I think it sucks that when I spend more than a few minutes composing a reply I can't post it. On more than one occasion I lost my reply this way.
So it's not a cosmetic problem. We're not talking about the minor nuisance of hitting refresh, we're talking about losing carefully crafted replies.
Fix it please.
- pg 18y agoIf you click on the back button, the text should still be there in the form you submitted. Surely your brower doesn't wipe forms when you click on back?
- Hexstream 18y agoYou'd be surprised, that has always been my instinctual reaction to those kinds of failures but oftentimes the textarea would just come back blank for some reason or something like that. I think it had to do with the "you can't go back because the page was generated from a POST operation" kind of message.
- gizmo 18y agoClicking back is not enough. You also have to refresh the page to get a new continuation. On IE the text is gone after you hit refresh. On firefox the text stays when you hit refresh. Since I'm used to the behavior of firefox... Printing the http-post data on the error page would also help. Because the moment I realize my post is gone I can still hit "forward" to get back to the error message. It's not a perfect solution, but since it only takes 15 seconds to implement it's a fair compromise.
- Hexstream 18y agoI took the habit of always copying my text to the clipboard before submitting anything substantial because between session timeouts, expired links and other failures there's just too many opportunities for your contribution to land in the bit bucket.