Bug 143276 - FILEOPEN DOCX Splitting a table in Word does not appear in Writers Manage Changes panel
Summary: FILEOPEN DOCX Splitting a table in Word does not appear in Writers Manage Cha...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.0.0.5 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, filter:docx, regression
Depends on:
Blocks: DOCX-Track-Changes
  Show dependency treegraph
 
Reported: 2021-07-09 10:16 UTC by NISZ LibreOffice Team
Modified: 2024-10-27 03:14 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
The example file with the table created in MS Word. (12.72 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2021-07-09 10:16 UTC, NISZ LibreOffice Team
Details
Screenshot of the document with the tables side by side in Writer and Word (52.28 KB, image/png)
2021-07-09 10:16 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-07-09 10:16:33 UTC
Created attachment 173472 [details]
The example file with the table created in MS Word.

FILEOPEN DOCX Splitting a table in Word does not appear in Writers Manage Changes panel

Splitting a table in Word with change tracking enabled is displayed in Words Reviewing Pane. In Writer, after opening this .docx file, the Manage Changes panel does not contain this information.

Steps to reproduce:
1.	Open attached .docx file in Word.
2.	In the Reviewing pane, we can see the changes (splitting the table).
3.	Open attached .docx file in LO Writer.
4.	Under the Manage Changes panel, this information disappears.

Actual results:
After opening the file in Writer, we can’t see the split in the Manage changes panel.

Expected results:
This information should be displayed in the Manage Changes panel like in MS Word.
Rejecting the change should merge the two tables, just like undoing a Split Table operation does.

LibreOffice details:
Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: bd2f2273d83dcca43eb6b465308707efd45e7adf
CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: hu-HU (hu_HU); UI: hu-HU
Calc: threaded

Also happens in 6.0, 5.0.
But not yet in 4.4: the insertion is visible, but rejecting it did not merge the two tables. Back then there was no Split tables button on the Tables toolbar, that was a new feature in 5.1.

Additional Information:
Bibisected using bibisect-win32-5.0 to:
URL: https://cgit.freedesktop.org/libreoffice/core/commit/?id=c4cf85766453982f1aa94a7f2cb22af19ed100be 

author Michael Stahl <mstahl@redhat.com> 2015-05-05 23:15:20 +0200
committer Michael Stahl <mstahl@redhat.com> 2015-05-06 00:10:17 +0200

sw: fix crash due to redlines on tables on ooo121112-2.docx
Comment 1 NISZ LibreOffice Team 2021-07-09 10:16:56 UTC
Created attachment 173473 [details]
Screenshot of the document with the tables side by side in Writer and Word
Comment 2 Buovjaga 2021-07-19 16:12:53 UTC
Confirmed

NixOS
Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: b1df9c67349cf4cc5be4128d797aefb87f50e38f
CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: x11
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Comment 3 Xisco Faulí 2022-05-03 12:24:18 UTC
Dear László Németh,
This bug has been in ASSIGNED status for more than 3 months without any
activity. Resetting it to NEW.
Please assign it back to yourself if you're still working on this.
Comment 4 QA Administrators 2024-10-27 03:14:09 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