Bug 38738 - EDITING: Screen focus and caret position modified after 'Tools > Update > All'
Summary: EDITING: Screen focus and caret position modified after 'Tools > Update > All'
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: Other Windows (All)
: low trivial
Assignee: Not Assigned
: 96612 105244 122728 (view as bug list)
Depends on:
Blocks: Writer-View-Jumps Text-Cursor
  Show dependency treegraph
Reported: 2011-06-28 01:41 UTC by Rainer Bielefeld Retired
Modified: 2022-08-16 04:00 UTC (History)
5 users (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 Rainer Bielefeld Retired 2011-06-28 01:41:28 UTC
Observed with with "LibreOffice 3.4.1RC1 - WIN7  Home Premium (64bit) German UI [OOO340m1 (Build:103)]"

Steps to reproduce:

0. Download and open sample document from
   "Bug 38703 - 'Update' deletes 'undo - redo' stack"
1. Click links in TOC one by one until caret is in line "Title3" (flickers in
   front of heading)
2. Menu 'Tools > Update > All'
   Expected: except update nothing happens, screen focus and
             caret position remain
   Actual: Focus changes to top of document, Caret is in TOC heading, many
           Formatting toolbars inactive May be because TOC is protected
           against manual changes)
           Navigation Toolbar inactive, what is not correct, it could be used
           to return to latest caret position. Green Navigation Toolbar arrow 
           reappears after click into document, but useless, stack has been 

Same problem with 'Update > Indexes'

For the additional problem that Navigation Toolbar stack has been lost I will file a separate report.
Comment 1 Florian Reisinger 2012-01-21 06:29:42 UTC
Confirmed with LibO 3,5rc1
Comment 2 Rainer Bielefeld Retired 2012-01-21 10:43:26 UTC
I also see that with "LibreOffice Portable 3.3.0  - WIN7  Home Premium (64bit) German UI [OOO330m19 (Build:6) tag libreoffice-]" 

Also with OOo 3.1.1, so inherited from OOo.

@Florian Reisinger:

Please feel free to reassign (or reset Assignee to default) if it’s not your area or if provided information is not sufficient. Please set Status to ASSIGNED if you accept this Bug.
Comment 3 A (Andy) 2013-05-04 20:39:56 UTC
@Rainer: What does "TOC" means?  Is my understanding of step 1 correct that to test this case you should place the cursor at the beginning of the heading "Test3"?

If my understanding is correct then this is for me reproducible with LO (Win7 Home, 64bit).
Comment 4 QA Administrators 2015-04-01 14:41:09 UTC Comment hidden (obsolete)
Comment 5 Buovjaga 2015-04-23 11:27:58 UTC
Confirmed with attachment 48452 [details].
TOC = table of contents.

Win 7 Pro 64-bit Version: (x64)
Build ID: f3375fa07f27bd2ade519af3c07d69040d10eaa9
TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-22_23:38:50
Locale: fi_FI
Comment 6 Robinson Tryon (qubit) 2015-12-13 11:21:29 UTC Comment hidden (obsolete)
Comment 7 Buovjaga 2015-12-26 14:41:31 UTC
*** Bug 96612 has been marked as a duplicate of this bug. ***
Comment 8 Buovjaga 2017-01-13 18:56:40 UTC
*** Bug 105244 has been marked as a duplicate of this bug. ***
Comment 9 QA Administrators 2018-01-14 03:24:47 UTC Comment hidden (obsolete)
Comment 10 Buovjaga 2019-01-19 18:40:47 UTC
*** Bug 122728 has been marked as a duplicate of this bug. ***
Comment 11 QA Administrators 2022-08-16 04:00:26 UTC
Dear Rainer Bielefeld Retired,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team