Bug 100667 - auto save loses scroll position
Summary: auto save loses scroll position
Status: RESOLVED DUPLICATE of bug 95797
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2016-06-29 04:15 UTC by Rich R
Modified: 2016-06-29 04:45 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Rich R 2016-06-29 04:15:50 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
Build Identifier: LibreOffice

steps to recreate:


Reproducible: Always

Steps to Reproduce:
1. settings: set autosave on at interval of n
2. use scroll wheel to scroll down any amount in a long document without anchoring the cursor in the newly scrolled-down viewing position.
3. autosave does a document save and reverts the view to the cursor position.
Actual Results:  
I lose my place, particularly when reviewing, editing, or proofreading documents because the cursor position and the view position may be several pages apart.

Expected Results:  
Leave the view as is on autosave, disregarding the cursor position so that I do not lose my place every n minutes where n=autosave interval.  

partial workaround is to either anchor the cursor every time you scroll or maybe use pg up and down instead.  Page up and down seem to not be affected, though not sure about that.  neither of these is very helpful since for me scrolling is the way I keep my place while proofing documents.  

[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes

Reset User Profile?No
Comment 1 Aron Budea 2016-06-29 04:45:50 UTC
Thanks for the report. This bug has already been fixed, and will be part of 5.2. The fix is not yet ported to 5.1, but I assume it's going to happen soon. See bug 95797.

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