https://bugs.documentfoundation.org/show_bug.cgi?id=160769
--- Comment #2 from [email protected] --- (In reply to Mike Kaganski from comment #1) > (In reply to BikeHelmet from comment #0) > > Expected Results: > > Both versions should recover all previously opened documents. > > No, they only should recover *changed* documents (which have something to > recover). Previously, LibreOffice confused people by suggesting them to > "recover" documents that had no changes (bug 57414). That was fixed in > version 24.2 (release notes at [1]). > > [1] https://wiki.documentfoundation.org/ReleaseNotes/24.2#Core_/_General This likely should be left to the user, giving them the option to recover all of them or only changed ones. It is very disruptive when LibreOffice crashes with the new behaviour. Here is a common scenario: -An office worker is looking at inventory / spreadsheets / reports before a Zoom meeting with higher up management. They are also referencing some new policy documents, so that they can discuss how the changes are going on-the-floor, and have other documents opened from previous discussions with employees/managers. Some resumes are also open, and they are evaluating possible new hires. (Maybe they a half dozen restaurants in a 60km area for a group of owners/shareholders?) In total there are about 30-40 documents open, enough that the recently opened list will not catch them all. The Zoom meeting starts. Things are going well for a few minutes. Then LibreOffice crashes abruptly. Upon restoring it, it does not reload all of the relevant documents, but only the changed ones. The employee has to scramble to locate and reopen things. The meeting takes almost 30 minutes longer due to having to find everything again. Everyone is annoyed. I cannot think of a business user that would want the new behaviour. I would make it a choice in the recovery dialog. Microsoft Office uses the old behaviour, which I think most business users and power users would consider correct. Since it was confusing enough to some users to create a bug submission and patch, I suggest expanding the recovery dialog to accommodate both use cases and expected recovery behaviours. You could even collect telemetry data on that, and discover exactly how many people expect each method. I suspect that it's more balanced than you'd assume. -- You are receiving this mail because: You are the assignee for the bug.
