After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 749943 - Geary Does Not Ask to Save, Nor Autosave, Drafts Before Closing
Geary Does Not Ask to Save, Nor Autosave, Drafts Before Closing
Status: RESOLVED DUPLICATE of bug 747627
Product: geary
Classification: Other
Component: composer
0.10.x
Other Linux
: High major
: 0.12.0
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-05-27 05:50 UTC by Johny Why
Modified: 2016-12-20 14:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Johny Why 2015-05-27 05:50:37 UTC
- I'm in compose mode, not popped out. 
- I receive a received-message alert.
- i click 'open' on the alert. 
- geary asks me "do you want to close the draft message?"

- first of all, WHAT? i'm not allowed to have a draft open and read another message at the same time? I understand, that's because of the way you implemented the interface-- requesting: please enable draft message to just stay there, in draft mode, if i open a new message. If it can even stay in edit-mode, great! if you have to save and close it, fine. 

- which brings us to the bug: 
- geary asks me "do you want to close the draft message, in order to read the new message you just tried to open?" 
- i click 'close the draft'. 
- geary does NOT automatically save my draft. geary does not ask me 'close and discard, or close and save?' Geary just closes it. 
- i just lost a bunch of work. Now i have to do my work all over again. Thanks, geary :(

- i believe asking people if they want to save something before they close it (or automatically saving it if you don't ask) is what people expect. And it's what should happen. 

- Moreover, if you autosave drafts (so that's the third request in this post-- please auto-save drafts while editing), then this never would have happened. i guess that's a dupe of #714074. Count me as +1 on that. 

- now i must go-- i have a lost email to re-create. 

I STILL LOVE GEARY  :)
Comment 1 Johny Why 2015-05-27 05:52:24 UTC
i know this is marked bug-- i consider not autosaving, or asking user to save, a draft before closing it is a bug. Not a programming bug-- a ux bug. 

oh yeah-- request: please let me keep a draft in edit mode when switching to another message. 

thx!
Comment 2 Johny Why 2015-05-27 07:12:10 UTC
sorry for many posts. Ask me, or autosave, either is better than losing work. 

The only high-priority item in my posts on this issue is not saving before closing the draft. Others are nice to have's. 

thx!
Comment 3 Johny Why 2015-05-27 07:12:40 UTC
(but i prefer autosave on drafts) THX!
Comment 4 Robert Schroll 2015-05-27 19:07:09 UTC
The long-term goal is to remove this dialog completely and have inline composers automatically instantiated for draft messages.  See bug #730486 and bug #743066.
Comment 5 Michael Gratton 2016-05-16 12:03:32 UTC
This is separate, but probably related, to bug #747627 - that's about the Save & Close button not actually working. This is about Save not even being presented as an option (and autosave not working).
Comment 6 Michael Gratton 2016-12-20 14:19:24 UTC
I think this should have indeed been fixed by Bug 747627, so I'm closing this as a duplicate. If that's not the case, please feel free to re-open this.

*** This bug has been marked as a duplicate of bug 747627 ***