OK that is a good point. A warning would not hurt. And attempting a relog if the post fails - yeah that might not be a heavy rewrite; at least it could be considered. I am pretty sure that you could get expirations in WX if you took too long to compose your post. It did try to log you back in; I don't remember this ever allow a post to go through successfully.

The only times I remember having problems posting with WX was when it was being wonky in other ways, as well, but I've always used the remember me feature, so it wouldn't have had to stop to put up the login page. I do know that others lost posts when WX wasn't being wonky. But with WX you could usually go back a page and retrieve the post.

Actually, I'm still more curious as to why the back (and forward) buttons don't work the way they're supposed to. On WX, if you just go back to the cached page. On the Phoenix, it always (except in Opera) treats it as a new page view, which has to have an effect on our bandwidth usage.

I realize that it may be good practice to compose long posts in a text editor, and then copy them into the posting box, but it's not a very user friendly solution.

What I've been doing, if I'm writing a long post, is copying it to the clipboard before I hit "post," so that if something does get messed up, I've still got it on my computer. Not as annoying as having to open a text editor.

Hmm.

Thread headers USED to display on every page, and there was a request to make that stop. So, like WX, that no longer happens. I'm against them being on every page, because it eats serious real estate.

Post delays -- this is interesting -- I've never had a problem. It will log you out after thirty minutes, but if you have "remember me" on, this shouldn't happen.

As for the stuff disappearing from the post box in IE and NN, this seems to be a server issue, not a code one, and it's something I'm currently researching.

I'm against them being on every page, because it eats serious real estate.

This seems a compelling argument to me, since the information is still available by going back to the first page.

I've had that lost post thing as well after leaving for a while and coming back. Hil's solution works for me.

Never made demo (see Natter). In terms of expiration, I suspect it tries to post before logging you in.

I suspect it tries to post before logging you in.

Nope. Must be something else.

Thread headers USED to display on every page, and there was a request to make that stop. So, like WX, that no longer happens. I'm against them being on every page, because it eats serious real estate.

Wrod with a side of wrod sauce. Please don't.

I've been using the test board to try and duplicate this timeout error, and so far can't.

Can I have more details? Browser version, length of delay between loading the page with the posting box and hitting the post message button? Is "remember me" set?

Mine was on IE, and I was away for about an hour and a half, with 'remember me' set.