Description: With an unsaved crash recovery, I start up LibreOffice. It offers to recover. I click Discard. Instead of simply discarding the Untitled document, LibreOffice pops up a second dialog asking where to save the discarded document. Don't do that! I explicitly told LibreOffice to discard the document. Don't second guess the user. Steps to Reproduce: 1. With an unsaved crash recovery, I start up LibreOffice. 2. It offers to recover. 3. I click Discard. 4. Instead of simply discarding the Untitled document, LibreOffice pops up a second dialog asking where to save the discarded document. Actual Results: see attached screenshot Expected Results: Don't pop up the second dialog Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36
Created attachment 135983 [details] screenshot of dialogs
Confirming, this behaviour has been like this for quite a while. Yes, it is annoying.
I've found this quite annoying as well. This additional dialog should have a checkbox that a user can check so they dont get disturbed again about this. If a user clicks 'cancel' or the dialog is not shown because the user asks for it not to be shown again, then LO should automatically save the files it can recover to the temp folder, so users can always go somewhere to still find the recovered files.
Start => Finish Discard => Are you sure? Yes/No X (nothing, but the recovery dialog comes up again even after another session has ended successfully) The situation should actually not happen, so we do not talk about the usual work flow. For safety reasons the confirmation makes a lot of sense. Just for discussion, I'm not happy about two clicks as well. Which is also true for Finish.
Removing needsUX as input has been given.
We had what seems a duplicate and unfortunately discussion started without checking first. But now that one is more actual so I mark this one as duplicate with regret. Please read carefully and see if more input is needed. *** This bug has been marked as a duplicate of bug 114508 ***