Help! Blogger is screwing up again!

Blogger recently announced the addition of an "Autosave" feature. Here's what it says on the Dashboard now:

As you work on a new or draft post in the Blogger post editor, the page will periodically send a copy of the text, title, labels, etc. to our servers. We do this about once a minute, unless you type a lot, in which case we'll save as soon as you stop typing, just to be on the safe side. You'll know it's happening because the "Save Now" button at the bottom of the page will turn into a gray "Saved" button.

We'll autosave new posts (they'll become drafts) as well as draft posts that you edit. We won't autosave posts that are currently published, since you don't want your readers to see your updates while you're working on them.

It would be so wonderful if only it were true!

I just lost a long post on my 'other' blog -- I was minutes away from completing what had been an hours-long project.

Yes, I did something stupid. I can't remember the ASCII code (ALT + nnn) for the character "§" -- the legal abbreviation for "section" as, in the case of the article on which I was working, a section of a statute.

So I compensated. I put it on the clipboard. I just had to hit CTRL-v and insert the "§" character into my text.

But I'm a WordPerfect guy. To get "§" on WordPerfect, I hit CTRL-w, 4, 6. I'm really used to hitting CTRL-w when I'm reaching for special characters.

But -- and here's a warning -- hitting CTRL-w while you are creating a new post in Blogger closes out your screen.

Ah! you say. That is precisely the sort of numbskull move that Blogger is trying to protect you against with the Autosave feature.

And, admittedly, the first time I made this error this morning my post was recovered with only the last sentence I had just typed not included.

But, a half hour ago, I did it again.

And now the post is gone. GONE. And who knows where it went? Not I, certainly. And, after messing around with entirely ineffective help screens before beginning this screed -- finding only laments from fellow users who have been similarly victimized without the ghost of a clue from Blogger as to how to undo the damage new Autosave has done -- I can only conclude that Blogger has no clue either.

I am just a tad peeved at the moment. Just a tad.

I am open for suggestions: Anyone know how to fix this? Does anyone know how to turn off this dangerous Autosave?