https://bugs.documentfoundation.org/show_bug.cgi?id=153405

            Bug ID: 153405
           Summary: Table in 2nd column wrongly split over page break;
                    unstable rendering
           Product: LibreOffice
           Version: 7.6.0.0 alpha0+ Master
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Created attachment 185140
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185140&action=edit
tablesplit1.odt (see STEPS TO REPRODUCE)

Sometimes tables are wrongly split across a page break and/or wrap into the
wrong column on the next page, and the splitting behavior is not stable over
save & reload.

Attached are a couple of test case .odt files.  Each of them started as a
single page containing a SECTION with two columns (so the text before the
section is single-column).   

The 2-column section contains several Tables (all but the first copy-pasted).  

=== CASE 1 STEPS TO REPRODUCE ===

1. Load attached tablesplit1.odt

Notice that the last table ("table #6") is split across the page break, but the
split-off portion appears in the SECOND column of the next page, not the first
column.   That is, the split portion of table #6 appears "after" table #7
(which is in the first column of the second page).

2. Put cursor in table #6
   Table->Properties->Text Flow

Notice that "Allow table to split across pages and columns" is NOT checked.

RESULTS: Table #6 wrongly split with the split-off portion landing in the 2nd
column of the next page, i.e. "after" Table #7

EXPECTED RESULTS: Table #6 should have forced a skip to the next page because
there is not enough room for it in the remaining space on the first page.

=== CASE 2 DESCRIPTION ===

Please see "exploded_screenshot.png" where the last table is split into many
pieces on several pages.   I got this after some sequence of inserts and
pasting of copies of the table which I can't reproduce.

After I did Save and then Reload, the rendering changed so that it was similar
to CASE 1 above.  Please see "after_save_reload.png".   Something about this
bug  makes rendering unstable across save & reload.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to