Created attachment 187106 [details] Screenshot shows the break in last row without content on following page Open the attached screenshot. There is shown a page break and a table. Table is set to Text Flow → Allow Row to break. Last row has been broken but there is no content on following row. Open the attached document (second attachment). There is needed font DejaVu to get this page break. Scroll to page 45/46. Might be you see header "Datentypen" at the top of page 46, might be you see the black border from the table of page 45 on top of page 46, might be this border will disappear after some seconds. Or it looks like the screenshot. If you can't see the bug: Click "Export directly to pdf". After exporting to pdf very often the buggy behavior appears: No header on top of the following page but an empty part of the last cells. This buggy behavior could appear on all versions here: LO 7.4.6.2, LO 7.5.3.2 and LO 7.6.0.0.alpha0 (2023-05-06).
Created attachment 187107 [details] Document, which shows this behavior on page 45/46 - Font DejaVu needed
There is a paragraph break in the row on the next page, deleting it, seems to solve the issue.
(In reply to m.a.riosv from comment #2) > There is a paragraph break in the row on the next page, deleting it, seems > to solve the issue. Have tried this before. Sometimes the paragraph sign is on the right column, sometimes on the left. No break there. Break would be shown at the end of the text and with a next paragraph sign for next paragraph. Just opened the document again: One black border (bottom of the table) on next page. Disappears after some seconds (nearby 10 seconds). Tried to export to *.pdf and after this export the empty line on next page appears again. It is also part of the exported *.pdf.
Got it working with LO 7.2.5 and LO 7.3.6. PDF-Export is as expected. Blank line doesn't appear. Saved the changed document and could also export it with LO 7.4.6.2. Then opened this document in LO 7.5.3.2 and the last row (together with content) of the table appears on next page. This is a reproducible error here: Opening with LO 7.3.6, save new - no bug. Open with LO 7.5.3.2: one row appears on the next page. Layout changed. Seems it is better for me to work with LO 7.4.6.2, because it will produce the same result as older versions. Set the version for this bug to LO 7.5.3.2.
About the new row on the next page, it looks fine with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 3bc7cc14706f47d740dfc5715970054922ca470c CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Version: 7.4.7.2 (x64) / LibreOffice Community Build ID: 723314e595e8007d3cf785c16538505a1c878ca5 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: threaded Version: 7.3.7.2 (x64) / LibreOffice Community Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL But doing an [Enter] with these versions adds two lines in the cell on the next page. While with the following version, adds only one line to the cell on the next page. Version: 7.2.7.2 (x64) / LibreOffice Community Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL What I see is going directly to page 46, just after open, there is a header's bottom line, which disappear after a few seconds or more. Sometimes going with page-down to page 46, the row on the next page it's visible. Maybe something it's updating or recalculated in the file, that gets this strange behavior. Also at opening, sometimes only show 1 of 41 pages, that gets updated after a few seconds. Tested without skia an antialiasing, nothing changes. Let's put as new.