For the love of Pete, please reconsider refreshing forum post pages to their default state when paging back and forth in the browser's history. It's so easy to lose a well thought-out post by accidently hitting an arrow key here, an enter button there. :-(
Ugh, I am sorry Louis *hugs*, I can only imagine why you are making this suggestion.
I second his request if it is possible!
This varies from website to website, I've gotten in the habit of typing my posts in notepad then copy pasting them, and keeping a copy until I know it has posted correctly, just in case the server doesn't respond, etc.
FWIW, this behavior is to an extent browser-dependent... in Firefox for instance, you do not lose your typed text if you hit "Back" and then "Forward."
LOL - Pete's not the only one this has happened to. For me it's probably a good thing - I probably only hit the post button on 60% of the messages I type up - most are intentionally abandoned. Kirbic is right though - it's not a website controllable thing (not easily anyway) - use Firefox.
I've gotten in the habit of typing my posts in notepad then copy pasting them, and keeping a copy until I know it has posted correctly, just in case the server doesn't respond, etc.
I do the same thing if I'm typing a long post, but with MS Word instead. My spelling is far worse than my posts betray. ;)
Hehe well to be completely honest I tend to use UltraEdit32 which has crash protection. However everyone has notepad so I suggested using that.
Originally posted by JMart:
Originally posted by togtog:
I've gotten in the habit of typing my posts in notepad then copy pasting them, and keeping a copy until I know it has posted correctly, just in case the server doesn't respond, etc.
I do the same thing if I'm typing a long post, but with MS Word instead. My spelling is far worse than my posts betray. ;)
Yeah I know it could be browser-dependant. It's just that IE is so freaking unpredictable when it comes to this particular issue. I was hoping it was an issue easily resolved. Damn it, I'm going to track this thing down and find out WHY it happens sometimes, happens not sometimes. (Or something.)
Yes, 'firefox' does it, but not 'outlook express', write or email 'outlook express', and suggest that they fixed this problem, as it can be done as 'firedox' has this, and I for one LOVE it..... I also love 'firefox', for showing me my spelling mistakes as well.....
FWIW, this behavior is to an extent browser-dependent... in Firefox for instance, you do not lose your typed text if you hit "Back" and then "Forward."
To an extent. I post to other forums (sorry) with this same browser, and when going Back and Forward, these sites are far more forgiving, as text is retained in the textarea.
Still, if I'm considering a longer post, I usually compose in a text editor and then cut and paste. That way too, I can run splel ckech.
I just fumble my way along until it either gets posted or disappears. Fwd and Back buttons seem to work all right for me with Safari, Mac. If I am going to type out a very long post, I will highlight and hold it in copy after every 5 or 6 lines, then I at least have most of it if I goof up, and can paste it in a new post to finish it.
If you are not handwriting a rough draft, then typing it into a text editor, spell-checking, referencing Wikipedia for factual accuracy and then pasting it in with relevant photos and links, well then you're basically just "phoning it in" anyway. Pffft. No dedication to the craft anymore.
If you are not handwriting a rough draft, then typing it into a text editor, spell-checking, referencing Wikipedia for factual accuracy and then pasting it in with relevant photos and links, well then you're basically just "phoning it in" anyway. Pffft. No dedication to the craft anymore.
Wikipedia??!! Don't you mean a REAL, made-outta-paper encyclopedia?
Sheesh, these youngun's and their newfangled shortcuts...
FWIW, this behavior is to an extent browser-dependent... in Firefox for instance, you do not lose your typed text if you hit "Back" and then "Forward."
Most of the time in IE, this is the case as well. Unless the server thinks the page "expired".
If this is an IE problem, it's not consistent. For example, this form retains the data you enter when paging back and forth between the page and some other page in your browser history. If others using Internet Explorer could check to see if they get the same results, I'd appreciate it.
So far, the only thing I've been able to come up with is that IE's caching mechanism is broken. Maybe.
