<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - FILESAVE: Auto save timing logic problem: can save too frequently" href="https://bugs.documentfoundation.org/show_bug.cgi?id=122530#c27">Comment # 27</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - FILESAVE: Auto save timing logic problem: can save too frequently" href="https://bugs.documentfoundation.org/show_bug.cgi?id=122530">bug 122530</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>(In reply to Luke Kendall from <a href="show_bug.cgi?id=122530#c26">comment #26</a>) > I also disagree that it should be measured from the first time the doc was > dirtied. I think it's far more useful to measure from the first time the doc > was dirtied *since the last save*. Probably that's what you meant? Every save makes the document "clean". The following save will make it dirty, which is the moment to detect and start counting. For the sake of auto-save, the moment of such auto-save also should mark the document as "clean" (only internally, for the purposes of the discussed problem; indeed, it should still the "unsaved edits" in UI, and ask for save on close - but it should not try to auto-save again until more edits make it internally dirty again).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>