When posting a reply and automatic log-in has expired, and the log-in screen appears after pressing the Preview Message button . . . after logging-in and the preview function continues, some of the post gets lopped off, both in the displayed preview area and in the editing box. I didn't notice exactly how much, it may be a specific number of lines that remains.
I've seen several cases in which somebody's post got cut off, and this is probably why. It wasn't noticed that part of the post was cut off, and the user continued on with posting the reply, not realizing what had happened.
It's possible the same thing happens if automatic log-in has expired when starting a new thread. I don't often start new threads and haven't run into that situation . . yet.
If anybody runs into this bug, just hit your browser's Back button several times to return to the original editing/entry screen, and the full text of the reply should be there. Log-in will remain in effect since the cookie is already set. Press Preview Message again and all should be well.
Note that I'm using Mozilla Firefox Version 1.0 Preview Release. I don't know if this bug may be specific to the Mozilla family. But I have evidence of the bug on other users' posts, and they probably don't use Firefox.
I've seen several cases in which somebody's post got cut off, and this is probably why. It wasn't noticed that part of the post was cut off, and the user continued on with posting the reply, not realizing what had happened.
It's possible the same thing happens if automatic log-in has expired when starting a new thread. I don't often start new threads and haven't run into that situation . . yet.
If anybody runs into this bug, just hit your browser's Back button several times to return to the original editing/entry screen, and the full text of the reply should be there. Log-in will remain in effect since the cookie is already set. Press Preview Message again and all should be well.
Note that I'm using Mozilla Firefox Version 1.0 Preview Release. I don't know if this bug may be specific to the Mozilla family. But I have evidence of the bug on other users' posts, and they probably don't use Firefox.