Bug 140860 - Open writer document doesn't position cursor where it was at previous close
Summary: Open writer document doesn't position cursor where it was at previous close
Status: RESOLVED DUPLICATE of bug 140147
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-07 15:47 UTC by George Deluca
Modified: 2023-02-05 09:05 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description George Deluca 2021-03-07 15:47:06 UTC 
Description:
Latest version (7.1.0.3) seems to have lost the ability to re-position the cursor as of the last document close.   Shift-F5 still will do the positioning, but the automatic positioning at Open seems to have been corrupted in the latest release.

Steps to Reproduce:
1.Open Doc and position cursor (at the end)
2.Close and restart Writer


Actual Results:
Cursor is NOT where it was at Close.

Expected Results:
Cursor should be at the bottom of the document


Reproducible: Always


User Profile Reset: No



Additional Info:
User data is properly filled in with Name etc.

Version: 7.1.0.3 (x64) / LibreOffice Community
Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Comment 1 [REDACTED] 2021-03-07 21:51:05 UTC 
repro

Version: 7.1.1.2 / LibreOffice Community
Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676
CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kf5
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

(after having reset user profile and adding user date in Tools -> Options -> LibreOffice -> User Data -> First/last name/initials)
Comment 2 [REDACTED] 2021-03-07 21:53:58 UTC 

*** This bug has been marked as a duplicate of bug 140147 ***
Comment 3 Aron Budea 2023-02-04 19:39:44 UTC 

*** This bug has been marked as a duplicate of bug 141586 ***
Comment 4 Aron Budea 2023-02-05 09:05:01 UTC 

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