<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - When the app is about to be terminated by the system, it should perhaps save the current document" href="https://bugs.documentfoundation.org/show_bug.cgi?id=128048#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - When the app is about to be terminated by the system, it should perhaps save the current document" href="https://bugs.documentfoundation.org/show_bug.cgi?id=128048">bug 128048</a> from <a class="email" href="mailto:contact@0x17.ch" title="Nicolas Christener <contact@0x17.ch>"> Nicolas Christener</a> <pre>I often run into out-of-memory situations on my Android phone and think it's quite a common situation on phones/tablets. I therefore suspect, that saving the document when the app gets stopped/killed by the system is the right thing to do. Maybe we could even get rid of the "save" button/menu entry and do the following things: * do an explicit save when using the back button "<" * auto save every 30s (or what ever it is at the moment) * save when the app gets stopped/killed by the user or system (kill the app) Pages on iOS doesn't have a save button as far as I can tell. MS Word on iOS does "Auto save" per default and the user can change it to manual save.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>