Bug 73955

Summary: Table with merged rows does not respect "Do not break across pages" setting
Product: LibreOffice Reporter: narayanaras
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: NEW --- QA Contact:
Severity: normal    
Priority: medium    
Version: 4.2.0.2 rc   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: Shows how merged Cell across multiple rows gets broken across a page-break

Description narayanaras 2014-01-23 05:48:48 UTC
Created attachment 92634 [details]
Shows how merged Cell across multiple rows gets broken across a page-break

When a table has merged rows, it does not respect the “Do NOT break row across page breaks” setting.

When some cells from multiple rows are merged, its very purpose is to show the data in these rows together, as an unbroken picture. But this intent is defeated when the merged cells are broken across page-breaks.

Desired: the "Allow rows to break across pages and columns" setting is unchecked (which means splitting of the row is NOT allowed), and if such a table has cells from multiple rows merged together, then all such rows should be treated as a single row.
Comment 1 A (Andy) 2014-03-16 14:22:08 UTC
reproducible with LO 4.2.1.1 (Win 8.1)

Steps to Reproduce:
1. Open WRITER
2. Go to TABLE -> INSERT -> TABLE
3. Let the columns at 2 and increase the numbers of rows for instance to 10 and press INSERT to insert the table
4. Write any little longer text into the rows of the first column so that the table goes over at least two pages
5. Go to TABLE -> TABLE PROPERTIES -> tab TEXT FLOW
6. Deselect "Allow row to brake across pages and columns"

Interim Result:
No row does break across pages.

7. Select two cells in the first column with the text (the last of page 1 and the first of page 2)
8. Make a right mouse click and go to CELL -> MERGE

Result:
Row crosses two pages despite the table properties.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.