Bug 108073 - Rest of table not shown if rows that aren't allowed to break overlap page break (until position changes)
Summary: Rest of table not shown if rows that aren't allowed to break overlap page bre...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 143607 (view as bug list)
Depends on:
Blocks: Writer-Table-Layouting
  Show dependency tree / graph
 
Reported: 2017-05-24 23:49 UTC by Aron Budea
Modified: 2025-04-06 03:10 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Attachments
Sample FODT (25.56 KB, application/xml)
2017-05-24 23:49 UTC, Aron Budea 		Details
Sample FODT saved as ODT (9.63 KB, application/vnd.oasis.opendocument.text)
2021-07-30 11:46 UTC, Aron Budea 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Aron Budea 2017-05-24 23:49:26 UTC 
Created attachment 133547 [details]
Sample FODT

Open the attached FODT document. It looks like a page with a one-row-table at the end of the 1st page.
Now add a line break before the table.

Magic, the table grew to its normal size!

Right-clicking certain rows, then opening Table Properties... / Text Flow reveals "Allow row to break across pages and columns" is disabled for the first two rows, and enabled for the rest of the table. If it gets enabled for the first two rows, the table displays correctly (a bit tricky to do, select the single row and the invisible row below, change the setting, save the file and reload).

The file can also be fixed in a text editor, see this part:

<style:style style:name="Table1.1" style:family="table-row">
   <style:table-row-properties fo:keep-together="always"/> <!-- this style: always to auto fixes it -->
</style:style>

The issue requires specific table positioning to occur.
Observed with 5.4beta1 and 4.0.0.3.
Comment 1 Buovjaga 2017-06-04 12:02:47 UTC 
It's a kind of magic

Arch Linux 64-bit, KDE Plasma 5
Version: 5.5.0.0.alpha0+
Build ID: c855400e9686ddd8bcba5691393f839f6f52c966
CPU threads: 8; OS: Linux 4.11; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on June 2nd 2017

Arch Linux 64-bit
Version 3.6.7.2 (Build ID: e183d5b)
Comment 2 Aron Budea 2017-06-04 17:23:21 UTC 
Note that this is not a file format issue, but a layout issue (the original case was a Word document).
Comment 3 QA Administrators 2018-06-05 02:38:46 UTC Comment hidden (obsolete)
Comment 4 Aron Budea 2019-04-17 01:28:27 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2021-04-17 04:07:34 UTC Comment hidden (obsolete)
Comment 6 Timur 2021-07-30 08:57:21 UTC 
Repro Lo 7.3+. Not Inherited because OO didn't open it, so I change to LO 3.3. 
Low because enter fixes a problem and it persists across save. But enter and undo and save keep the problem.
Comment 7 Aron Budea 2021-07-30 11:46:55 UTC 
Created attachment 173976 [details]
Sample FODT saved as ODT

(In reply to Timur from comment #6)
> Repro Lo 7.3+. Not Inherited because OO didn't open it, so I change to LO
> 3.3. 
As I mentioned, this is a layout issue, not a file format issue, have you tried with the FODT saved as ODT first? I can repro with that even in OO 3.3.0.

And the user shouldn't be expected to do any kind of gynmastics on their file, it should open with the fidelity that is expected. This is a minimized sample, but if it were a 20+ page document with a truncated table somewhere, the user might not even notice something is wrong until scrutinizing the document in detail.
Comment 8 Aron Budea 2021-08-22 01:15:52 UTC 
*** Bug 143607 has been marked as a duplicate of this bug. ***
Comment 9 Stéphane Guillou (stragu) 2023-04-06 10:07:22 UTC 
Reproduced as described in recent master build:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 5cc29848b78b6c5ab01aa7a66b1dd7caff5f9385
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded
Comment 10 QA Administrators 2025-04-06 03:10:45 UTC 
Dear Aron Budea,

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