We probably won't be able to force the draft to be cleared when a user with the prevent_accidental_unload preference enabled confirms that they do want to navigate away from a not-yet-finished post, but not much we can do about that. The prevent accidental unload feature isn't going anywhere; in my opinion, a confirmation dialog is a great UX improvement over the all-but-guaranteed heart attack that an accidental unload usually causes.
Also, from now on, we won't be hard-wrapping commit messages at 72 characters anymore.
SweClockers just announced the addition of a native autosave draft feature inspired by the one in BSC! Unlike our feature, it's server-side (an improvement if anything) and loads autosaved drafts automatically (seems like an improvement), but just like us, it autosaves every three seconds and doesn't save very short drafts.
We probably won't be able to force the draft to be cleared when a user with the
prevent_accidental_unloadpreference enabled confirms that they do want to navigate away from a not-yet-finished post, but not much we can do about that. The prevent accidental unload feature isn't going anywhere; in my opinion, a confirmation dialog is a great UX improvement over the all-but-guaranteed heart attack that an accidental unload usually causes.Also, from now on, we won't be hard-wrapping commit messages at 72 characters anymore.