jhuggett":0x2gfzy2 said:
I don't know... sounds like a Mac problem to me. :twisted:
Jason:
Actually, I think you're partly right. I'm running OS X 10.4.11, and if I click out of a text entry field on a "Post a reply" page on this BB, it's the functional equivalent of hitting the "Back" button. Clicking on the "Forward" button returns me to the "Post a reply" page. It works that way in every browser I've tried except Mozilla Navigator v1.7.13; for some reason, the Delete key is not mapped to the "Back" function in that browser (but if you hit the "Back" button, you'll still lose your text, when you return to the page.
LL, Gregorio:
The fact that you're losing your text when you come back to the page after unintentionally going "Back" by hitting the Delete key is probably specific to your browser, or at least to the way your browser preferences are set. In several browsers, I've tried typing in the subject line and message body text boxes, clicking out of them to disable the text entry cursor, then hitting the Delete key, and then the Forward button to return to the "Post a reply" page. For the following browsers, my text is still there when I come back, which means the browser has cached the entire page and any text I've entered, and it's reloading it from my cache, not from the site:
- Safari - v3.0.4
- Shiira - v2.2 (build 070718)
For the following browsers—all of which are built on the Mozilla 1.8 trunk—any text I have entered is gone when I come back:
- SeaMonkey Navigator - v1.1.7
- Mozilla Navigator - v1.1.19
- Firefox - v2.0.0.11
- Camino - v1.5.4
If there's a preferences setting that will force the browser to cache the text I enter and reload it on any of those apps, I haven't found it yet.
There are a couple of workarounds, though. If you Preview the message before you've hit the Delete key, then the browser will load the preview into a cache. When you return to the page after hitting the Delete key, you'll get a prompt asking whether you want to reload the page from the last cached version (the one you last Previewed). Click "OK". It won't recover any text you might have typed since the last time you clicked "Preview", but it will at least keep you from losing everything, and it does load the saved Preview content into message body text entry pane.
For my part, I use the embedded composer only when I write short messages. Scrolling is a pain when I write long messages, and the text isn't particularly easy to read in the text entry pane...especially now that we're back to using the older version of phpBB. I usually just compose my messages in TextEdit, because I save them to my local directory anyway. If I have a lot of BBcode to enter, I might do that in the embedded composer (highlighting the affected text and clicking the formatting buttons is easy, but even there, if I have to do a lot of scrolling, I'll usually just enter the BBcode manually as I compose the message. The problem with the embedded composer is that the sumbitch won't stay scrolled. Every time you make a formatting change, the #@!%&)? piece o' crap snaps back to the top of the text entry field. Grrrrrr... :evil: :x What moron designed that?! Ditto for the emoticons insertion function. No matter where the cursor is, the friggin thing always inserts at the end of the message. Stoopid.
Anyhow, composing the post in TextEdit is my solution, and then I copy and paste into the "Post a reply page". In that way, I can increase the font size to one I can easily see, and still control the page size so I can see more than the relatively small space provided by the doggone embedded composer. I've never been very comfortable working in a browser window anyway. Seems too volatile a platform for anything I want to keep for me to entrust my work to it.
Vito :joker: