GNOME Bugzilla – Bug 743067
Properly restore state of drafts
Last modified: 2015-01-17 00:44:17 UTC
Currently drafts are restored into an inconsistent mix of INLINE and INLINE_NEW.
Created attachment 294714 [details] [review] Properly restore state of drafts We do this heuristically, by noting which messages it is in reply to and seeing if it matches the unmodified reply or reply all states. This isn't perfect; notably forwarded messages are picked up. We hide the existing draft in the conversation viewer as soon as we open the composer. We also ensure that future versions of this draft will also be hidden. The list of emails to be hidden is cleared when the conversation viewer is, so we query all open composers at this point to see which email ids should be hidden.
Created attachment 294715 [details] [review] Properly restore state of drafts Sometimes we end up passing a null id to the blacklist code. I'm not sure why this happens, but let's no freak out when it does.
Review of attachment 294715 [details] [review]: Commit!
Attachment 294715 [details] pushed as 0958273 - Properly restore state of drafts