Bug 122796 - Compare Document will misplace the first whole paragraph deletion at the end of attached DOCX documents
Summary: Compare Document will misplace the first whole paragraph deletion at the end ...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.6.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Document-Comparison
  Show dependency treegraph
 
Reported: 2019-01-18 04:47 UTC by Cuong Tran
Modified: 2023-06-05 03:13 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
Test original document (5.65 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2019-01-18 04:58 UTC, Cuong Tran
Details
Test revised document (5.43 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2019-01-18 04:58 UTC, Cuong Tran
Details
Comparing output (5.89 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2019-01-18 04:59 UTC, Cuong Tran
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Cuong Tran 2019-01-18 04:47:59 UTC
Description:
Bug in comparing documents: If the first change (with regard to the change position in document) is a whole paragraph deletion, that deletion will be misplaced at the end of the document. The second and following deletions look fine. All insertions look fine. If the first change is not a whole paragraph deletion (e.g., partial text deletion), everything looks fine. 

Steps to Reproduce:
1. Use any example *.docx with some paragraphs in its content
2. Make a copy of that docx as a revised version
3. Edit the revised version. Make sure that **deleting a whole paragraph** is the first change (with regard to the change position in document)
4. Compare the revised version with the original docx

Actual Results:
The first whole paragraph deletion will appear at the end of the document (incorrect) while other editings would appear at correct places

Expected Results:
The first whole paragraph deletion should appear correctly at where it actually happens


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Cuong Tran 2019-01-18 04:58:04 UTC
Created attachment 148412 [details]
Test original document
Comment 2 Cuong Tran 2019-01-18 04:58:43 UTC
Created attachment 148413 [details]
Test revised document
Comment 3 Cuong Tran 2019-01-18 04:59:13 UTC
Created attachment 148414 [details]
Comparing output
Comment 4 Dieter 2019-01-18 08:22:34 UTC
I can't confiirm it with

Version: 6.3.0.0.alpha0+ (x64)
Build ID: 411f3a050ac2be598019d512f8ccfe041080c28f
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2019-01-14_03:17:11
Locale: en-US (de_DE); UI-Language: en-US
Calc: threaded
Comment 5 Cuong Tran 2019-02-11 05:13:09 UTC Comment hidden (obsolete)
Comment 6 Timur 2019-02-11 11:22:07 UTC Comment hidden (obsolete)
Comment 7 Cuong Tran 2019-02-11 19:22:52 UTC Comment hidden (obsolete)
Comment 8 Timur 2019-02-12 09:06:51 UTC
Steps shouldn't assume something is obvious:
0. Open attachment 148412 [details] DOCX in Writer and delete the whole paragraph "Etiam bibendum.." and save as revised version 
1. Open revised or attachment 148413 [details] DOCX in Writer
2. Edit - Track Changes - Compare Document to original attachment 148412 [details] DOCX

Actual Results:
The first whole paragraph "Etiam bibendum.." deletion will appear at the end of the document (incorrect) while other editings would appear at correct places
Expected Results:
The first whole paragraph deletion should appear correctly at where it actually happens (as the 2nd paragraph)

Note: reverse compare works right.
3. Open original attachment 148412 [details] DOCX in Writer
2. Edit - Track Changes - Compare Document to revised attachment 148413 [details] DOCX
Actual and Expected Results:
The 2nd paragraph is marked as added. 

Repro LO 3.6 and 6.3+. Not regression.
Comment 9 QA Administrators 2023-06-05 03:13:50 UTC
Dear Cuong Tran,

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