Bug 138083 - FILEOPEN DOCX Change tracked, moved TOC accept/reject leaves empty TOC
Summary: FILEOPEN DOCX Change tracked, moved TOC accept/reject leaves empty TOC
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.1.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
Depends on:
Blocks: DOCX-Track-Changes
  Show dependency treegraph
 
Reported: 2020-11-09 10:07 UTC by NISZ LibreOffice Team
Modified: 2024-07-28 03:15 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Example file from Word with moved TOC (15.38 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2020-11-09 10:07 UTC, NISZ LibreOffice Team
Details
Screenshot of the original document side by side in Word and Writer (136.85 KB, image/png)
2020-11-09 10:07 UTC, NISZ LibreOffice Team
Details
Screenshot of the original document side by side in Word and Writer after accepting all changes (102.42 KB, image/png)
2020-11-09 10:07 UTC, NISZ LibreOffice Team
Details
Screenshot of the original document side by side in Word and Writer after rejecting all changes (88.57 KB, image/png)
2020-11-09 10:08 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NISZ LibreOffice Team 2020-11-09 10:07:20 UTC
Created attachment 167115 [details]
Example file from Word with moved TOC

Attached example file was created in Word, it has a few heading-formatted paragraphs and a TOC made from these.
Change tracking was enabled and the TOC was cut and pasted a few paragraphs below.
When opened in Writer and accepting/rejecting the change an empty TOC remains.

Steps to reproduce:
    1. Open attached file
    2. Accept or reject all changes

Actual results:
An empty TOC remains at the deleted/inserted position.

Expected results:
No empty TOC after accept/reject.

LibreOffice details:
Version: 7.1.0.0.alpha1+ (x64)
Build ID: 00e5c63c35307faacf76a5e2ca7953c4208244ed
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: hu-HU (hu_HU); UI: en-US
Calc: CL

also happens in:
Verzió: 6.1.0.3
Build az.: efb621ed25068d70781dc026f7e9c5187a4decd1
CPU szálak: 4; OS: Windows 6.3; Felületmegjelenítés: alapértelmezett; 
Területi beállítások: hu-HU (hu_HU); Calc: CL

Move is not supported as delete/insert in 6.0/older versions.
Comment 1 NISZ LibreOffice Team 2020-11-09 10:07:42 UTC
Created attachment 167116 [details]
Screenshot of the original document side by side in Word and Writer
Comment 2 NISZ LibreOffice Team 2020-11-09 10:07:59 UTC
Created attachment 167117 [details]
Screenshot of the original document side by side in Word and Writer after accepting all changes
Comment 3 NISZ LibreOffice Team 2020-11-09 10:08:14 UTC
Created attachment 167118 [details]
Screenshot of the original document side by side in Word and Writer after rejecting all changes
Comment 4 Dieter 2020-11-29 07:18:41 UTC
I confirm it with

Version: 7.0.3.1 (x64)
Build ID: d7547858d014d4cf69878db179d326fc3483e082
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL
Comment 5 QA Administrators 2024-07-28 03:15:05 UTC
Dear NISZ LibreOffice Team,

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

MassPing-UntouchedBug