Not sure if posting this will even work, but it's worth a try.
EDIT: ok since posting this it's working again. So please ignore this. I'll leave it up in case anyone else had the issue - maybe posting something fixes it.
I think that you were submitting while either forwardslash or I were pushing out an update. forwardslash is in BC while I am in Michigan. As of late, I am doing most of my coding first thing in the morning while he is doing it at an ungodly hour on the West coast. I committed some code this morning, then tried to push it out, only to find that forwardslash committed some of his own in few seconds or so in between. In short, we were both pushing code out today at about the same time. We are going to have to get disciplined about pushing non-emergency updates out once per day at most, and hopefully at the slowest traffic hour. That being said, I think that I am going to add a 'copy to clipboard' link under the text field. It might be worth clicking it before submitting a magnum opus of a reply.
I've had the same issue if I stay on a page for a while. It's infuriating to type a comment, click submit and POOF, it's gone. Maybe don't leave the page when the submission is unsuccessful? It would be nice to have a safer mechanism for this.
When this happens hitting the back button should return you to the submission with your comment in place. You'll just need to copy/paste it and resubmit it from there. But yes, it is frustrating.I've had the same issue if I stay on a page for a while. It's infuriating to type a comment, click submit and POOF, it's gone.
Thanks, didn't know you could do that. However, it would still be nice if this was a bit more intuitive.