Bug 157852 - Table Rows do not split across page with specific position and Repeat heading not Row break
Summary: Table Rows do not split across page with specific position and Repeat heading...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1 all versions
Hardware: All All
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Writer-Tables
  Show dependency treegraph
 
Reported: 2023-10-20 11:29 UTC by StamatisZ
Modified: 2023-11-21 12:30 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Test document with error (21.50 KB, application/vnd.oasis.opendocument.text)
2023-10-20 11:30 UTC, StamatisZ
Details

Note You need to log in before you can comment on or make changes to this bug.
Description StamatisZ 2023-10-20 11:29:06 UTC
Description:
A table in the document is only partially shown. The lower 2 rows are missing.

Steps to Reproduce:
1. Open attached document (test2.odt)
2. Scroll down to end of first page

Actual Results:
Table 3 shows one row below the title

Expected Results:
Table 3 should display 3 rows below the title


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: threaded
Comment 1 StamatisZ 2023-10-20 11:30:41 UTC
Created attachment 190336 [details]
Test document with error
Comment 2 raal 2023-10-20 22:22:48 UTC
Repro with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 3649dc202bedf72e37c77993a1f7027bfdfc6d9e
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded


When I unclick "Repeat heading" or click "Allow row to break accross pages and columns" in table properties, then all rows appears.

In Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) is table rendered on second page.
Comment 3 raal 2023-10-20 22:37:14 UTC
bisected with bibisect-41max [linux] to  25e5e68d27a53133d884691e880dbdc186610577 is the first bad commit
commit 25e5e68d27a53133d884691e880dbdc186610577
Author: Matthew Francis <mjay.francis@gmail.com>
Date:   Fri Sep 18 11:10:18 2015 +0800

    source-hash-f9560c8f9982eaef09b74baa479c187f049c4f9e
    
    commit f9560c8f9982eaef09b74baa479c187f049c4f9e
    Author:     Khaled Hosny <khaledhosny@eglug.org>
    AuthorDate: Sat May 11 07:07:29 2013 +0200
    Commit:     Khaled Hosny <khaledhosny@eglug.org>
    CommitDate: Sat May 11 08:55:39 2013 +0200
    
        Cleanup FreeType ascender/descender handling a bit

Not sure if it's relevant. Before this commit is table on first page, after the commit the bug appears, but maybe only sizing of font was changed and there is not enough area to show rows? cc to Khaled.
Comment 4 ⁨خالد حسني⁩ 2023-10-21 09:58:44 UTC
The original report was on Windows, the bisected commit is a Unix-only change (and code that is long gone, anyway).
Comment 5 raal 2023-10-21 10:51:00 UTC
(In reply to ⁨خالد حسني⁩ from comment #4)
> The original report was on Windows, the bisected commit is a Unix-only
> change (and code that is long gone, anyway).

Thanks Khaled. Deleting regression tags. Probably as a coincidence, it's just about height of row and position of the table. For example when I change font size inside table to 6 pt, the table is correctly rendered on second page and all rows are visible. Still the bug, rows should not disappear.
Comment 6 ⁨خالد حسني⁩ 2023-10-21 12:30:44 UTC
(In reply to raal from comment #5)
> (In reply to ⁨خالد حسني⁩ from comment #4)
> > The original report was on Windows, the bisected commit is a Unix-only
> > change (and code that is long gone, anyway).
> 
> Thanks Khaled. Deleting regression tags. Probably as a coincidence, it's
> just about height of row and position of the table. For example when I
> change font size inside table to 6 pt, the table is correctly rendered on
> second page and all rows are visible. Still the bug, rows should not
> disappear.


I think the bug here is that a table that should be split across pages is not split, if you change the table settings to not split, it will move to the next page and all rows will appear.