Wedge

Sounds good to me, though I'd not actually had any problems on iOS with my iPad, curiously enough. I'm starting to wonder if iPad 1 / iOS 5.0 does things a bit differently to everyone else :-/

Dunno. That's a possibility.
I'd be most interested in knowing if anyone else's getting the problem I have on my 4.2 -- unresponsive keyboard when I tap a textarea or input box. Because as of now, I have no idea how to fix that...

Okay, I'm done with my commit -- won't spend more time today on drafts and blog posts, so if you want to look into the 'recent posts first' bugs, please do it... :) (That's valid for anyone ;))

I also didn't touch the menu icon overlay code -- just forgot about it. And I'm still a bit wary of touching that area again... (Just like I was wary about touching Class-CSS.php this morning, as it's grown to be so complex :P)
So, if anyone could remind me to do it later...

Sorry, but for me it doesn't work. Even if i "save it as draft".
The only message i get:


You have no draft messages saved at this time

Hmm, it seems to be working for me just fine?

If you happen to post between the first AJAX submission and it coming back, it won't be deleted because it won't have the id to delete. What we could do, potentially, is block posting while sending off the AJAX request, but if there's a problem it's still going to disappear into the aether like that.

Imagine that: clicking the submit button right when the autosave triggers.
It's only a problem for a week at the most, though.

Sure, and it's not like the odds are that high of doing it either, maybe just bad luck :/

I'd note that disabling the save button is exactly what WP does when autosaving drafts but of course that's a slightly different context in which to do it.

Suggesting an improvement for drafts...

I submitted a post and got a "There was a reply..." message and the full post again.
I then got a browser crash while opening Dragonfly. (Thank you, Opera 12...)
I restarted, and my draft only had half of the post.

So my suggestion would be to save the draft automatically when you hit Preview or you get an error message and the full post page.
What do you think...?

Seems meaningful enough, shouldn't be a big deal - in theory there will already be a draft id to work with at that point. The trick is to seamlessly fold it into the different routes of saving drafts.

(And that's where my expertise stops dead... :P)

You know what, though? I wrote the damn thing and I only barely remember how I did it :P