Bug 140264 - FILEOPEN DOCX Moved numbered paragraph does not leave empty paragraph in tracked changes
Summary: FILEOPEN DOCX Moved numbered paragraph does not leave empty paragraph in trac...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.3.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
Depends on:
Blocks: DOCX-Track-Changes
  Show dependency treegraph
 
Reported: 2021-02-08 13:52 UTC by NISZ LibreOffice Team
Modified: 2025-08-24 03:11 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file from Word with moved numbered paragraphs (15.91 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2021-02-08 13:52 UTC, NISZ LibreOffice Team
Details
Screenshot of the original document side by side in Word and Writer (141.85 KB, image/png)
2021-02-08 13:54 UTC, NISZ LibreOffice Team
Details
Screenshot of the original document side by side in Word and Writer with hidden changes (140.47 KB, image/png)
2021-02-08 13:55 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 2021-02-08 13:52:56 UTC
Created attachment 169585 [details]
Example file from Word with moved numbered paragraphs

Attached file was made in Word by moving two numbered paragrapsh in it:
- the second (Nunc Viverra) is marked completely deleted in Word including its numbering. This is opened correctly in Writer.
- The originally sixth (Etiam eget dui) is marked deleted without its numbering and leaves an empty numbered paragraph in Word. This is opened incorrectly without the empty paragraph. This causes the subsequent numbered paragraphs to have an incorrect numbering.

Steps to reproduce:
    1. Open attached file

Actual results:
No empty paragraph where “Etiam eget” was moved from. Last number is 10 instead of 11.

Expected results:
Same look as in Word.

LibreOffice details:
Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 44b914b1e2616ca8f70e896e653a46ca93610234
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win
Locale: en-US (hu_HU); UI: en-GB
Calc: CL

Also in:
Version: 6.3.0.4 (x86)
Build ID: 057fc023c990d676a43019934386b85b21a9ee99
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
Locale: hu-HU (hu_HU); UI-Language: en-US
Calc: CL

Differently bad (both deletions left an empty numbered paragraph) in:
Version: 6.2.0.3
Build ID: 98c6a8a1c6c7b144ce3cc729e34964b47ce25d62
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
Locale: hu-HU (hu_HU); UI-Language: en-US
Calc: threaded
Comment 1 NISZ LibreOffice Team 2021-02-08 13:54:46 UTC
Created attachment 169586 [details]
Screenshot of the original document side by side in Word and Writer
Comment 2 NISZ LibreOffice Team 2021-02-08 13:55:21 UTC
Created attachment 169587 [details]
Screenshot of the original document side by side in Word and Writer with hidden changes
Comment 3 mulla.tasanim 2021-02-08 17:04:35 UTC
Thank you for reporting the bug.

I can confirm the bug present in

Version: 7.0.3.1 (x64)
Build ID: d7547858d014d4cf69878db179d326fc3483e082
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL

Version: 7.2.0.0.alpha0+ (x64)
Build ID: 761a672d62df1891b9f4f367a499b220ab2b33fa
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL
Comment 4 QA Administrators 2023-02-09 03:25:04 UTC Comment hidden (obsolete, spam)
Comment 5 Piotr 2023-06-07 08:02:25 UTC
I checked, I can confirm the bug exists. Paragraph numbering is different in LO Writer than in Word. The version I checked with:

Version: 7.6.0.0.alpha1+ (x86) / LibreOffice Community
Build ID: 1c98c88a1208f47327ac2f3beaf593521ce9b394
CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: pl-PL (pl_PL); UI: en-US
Calc: CL threaded
Comment 6 QA Administrators 2025-08-24 03:11:41 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