Saved Drafts for New Post Replies
That's right! When you go to compose a reply post, you'll notice some new UI for automatically saving what you're writing. The way this works is that we'll save your contents automatically 3 seconds after you pause typing. You can also initiate a save manually, though you usually shouldn't need to. This will work in the the Rich Text Editor, the BBCode Editor, and on Mobile.
Once a reply draft is saved, all you need to do is come back to the thread where you had drafted a reply, at some point in the future, and you'll find your draft waiting for you in the Reply editor. This will work if you draft on one computer and then return to the thread via another computer. It will also work across Mobile & Desktop. Drafts are saved server-side.
You can draft one post reply at a time for any given thread. There's not currently a way to work on a long-term draft but still fire off a quick reply in the meantime. Until you publish your draft, it will occupy the reply editor's entry field. However, you can have a draft saved for each of as many threads as you like. You're not just limited to one single draft, period.
This is a first stage rollout: there is no draft saving for anything other than new replies. No drafts for new threads, no drafts for private messages or articles, comments, reviews, etc. There is also no draft saving of edits to posts.
We do plan to expand draft coverage soon, and we built the architecture in a way that will make this easy to spread to more areas. But we want to prove out the fundamentals of this functionality in one place first. There is also currently no "My Drafts" page, although that will be come a necessity as we expand Draft functionality to more use cases.
For now, it's for new replies only - just go back to the thread, and your draft in progress will be where you left it. This does mean that you'll see the "unsaved changes" warning a lot less - we don't pop that warning if your draft contents have been saved.
The Fix List
#14282: Some notable browsers like iOS Safari and IE8 drop URL hashes during a redirect. This was causing some of our email notifications to click through to the wrong post. We're using a hashless virtual URL in all our outgoing emails temporarily, until these browsers resolve this issue.
#14584: Very large thread albums will now be more reliably viewable in the Mobile lightbox.
#14644: Belarus' decision to update their daylight savings time policy will now be reflected in our database of timezones and their associated offsets.
#9650: We removed some of the more egregious CSS backflips we used to do for IE6 and IE7. This means lighter pages for all, and perhaps significant breakage for anyone still on these ramshackle browsers. In the holiday spirit, I will personally gift a copy of a modern browser to any affected user.