Bug 135632 - LAYOUT DOCX Table last rows content does not show up in multi page non-floating table
Summary: LAYOUT DOCX Table last rows content does not show up in multi page non-floati...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, filter:docx, regression
Depends on:
Blocks: DOCX-Tables
  Show dependency treegraph
 
Reported: 2020-08-11 10:54 UTC by NISZ LibreOffice Team
Modified: 2025-05-15 03:12 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot of the original document side by side in Word and Writer (76.75 KB, image/png)
2020-08-11 10:54 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-08-11 10:54:16 UTC
Created attachment 164150 [details]
Screenshot of the original document side by side in Word and Writer

When opening attachment #154864 [details] (from bug #127118) the table numbering slips on the second page: topmost cell is empty, and the bottom most contains numbering only up to 30 instead of 31.


Steps to reproduce:
    1. Open attachment #154864 [details] 

Actual results:
Second page starts with an empty table cell in the second column, numbering goes only until 30.

Expected results:
No empty cell and numbering goes to 31.

LibreOffice details:
Version: 7.1.0.0.alpha0+ (x64)
Build ID: <buildversion>
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win
Locale: hu-HU (hu_HU); UI: hu-HU
Calc: CL

(yesterdays nightly)

But not yet in 6.3.

Additional Information: 

Bibisected using bibisect-win64-6.4 to:
URL: https://cgit.freedesktop.org/libreoffice/core/commit/?id=3cccdabf19a99fd3f657985c1822436d7679df2b 
author	László Németh <nemeth@numbertext.org>	2019-11-19 21:12:28 +0100
committer	László Németh <nemeth@numbertext.org>	2019-11-22 08:00:45 +0100

tdf#125300 extend AddParaSpacingToTableCells with line spacing

Adding CC to: László Németh
Comment 1 NISZ LibreOffice Team 2020-08-11 11:08:18 UTC
Also: copying a word from the vertical cell and pasting it before the table corrects the layout.
Comment 2 Xisco Faulí 2020-08-11 11:31:39 UTC
Reproduced in

Version: 7.1.0.0.alpha0+
Build ID: 0de191e1d201d691c2196cf1aef412a98affb66f
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 3 Justin L 2021-03-24 18:17:21 UTC
repro 7.2+
Comment 4 Czeber László Ádám (NISZ) 2023-05-15 13:04:22 UTC
Notes on reproduction:
- The error only appears for the min-row-height parameter in the row style
- Applying a minimal or optimal row height removes the layout error (the min-row-height parameter is deleted)
- If there is no merged cell at the beginning or the table is not two columns, it cannot be reproduced
- If there is more than one row of text in the cells, the error is also not reproduced

It is likely that the layout error bounces between two states until it the loop detection stopped it, but this causes the table elements to be drawn in two different states.
Comment 5 QA Administrators 2025-05-15 03:12:27 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