Why Writer can split a long Keep with next chain
By ON Lab · Sources checked November 8, 2026
If Keep with next is enabled throughout a long run of Writer paragraphs, it creates a connected chain rather than a priority for one particular heading. In our compact native fixture, enabling it everywhere still split the heading from its following paragraph. Keeping only the intended heading linked allowed that pair to move together.
A reader's numbered paragraph separated from the next paragraph despite the setting. The discussion identified a long chain of inherited keep attributes. We tested the effective paragraph behavior separately with original text and controlled page geometry, rather than claiming to repair the reader's actual document.
Two text-flow controls solve different problems
Writer's official Text Flow help separates keeping a paragraph with its successor from allowing a paragraph itself to split. The current API makes that distinction explicit:
| Property | Meaning relevant here |
|---|---|
ParaKeepTogether=True | Keep this paragraph joined to the following paragraph |
ParaSplit=False | Prevent this paragraph itself from splitting across pages |
A link to the next paragraph is not a rule that identifies the most important heading in a larger chain. If several consecutive paragraphs each link to the next one, the connected content may exceed the available page height.
The same content under three configurations
Our native Writer test contained twelve short, one-line paragraphs. Paragraph 8 was the heading; paragraph 9 was its intended following detail. The page was deliberately compact: 16 × 10 cm, with 1 cm margins, 12-point text and a 5 mm paragraph bottom margin.
We held the text and page geometry constant, exported each case to PDF to lay out the document, and inspected the paragraphs' page positions through the native view cursor.
| Keep-with-next configuration | Heading 8 page | Detail 9 page |
|---|---|---|
| No links | 1 | 2 |
| All paragraphs except the last linked | 1 | 2 |
| Only heading 8 linked | 2 | 2 |
The all-linked case was longer than a page and still broke between paragraphs 8 and 9. It did not encode the author's preference for preserving that particular pair. Allowing breaks elsewhere let the heading and detail move to page 2 together.
All three fixtures ended on page 2. The objective was the placement of the intended pair, not reducing the total page count.
Inspect the surrounding chain, not only the stranded heading
- Work on a saved copy and display enough neighboring paragraphs to see the intended group.
- Inspect Text Flow for the heading and several paragraphs before and after it.
- Identify which paragraphs genuinely need to stay with their successors.
- Allow breaks at suitable detail-level boundaries instead of applying the link to the whole run.
- Keep the intended heading linked to its first detail paragraph, then inspect pagination again.
If a style supplies the setting, inspect that style and its inheritance as well as direct paragraph formatting. A style change can affect many paragraphs or alter what a child style inherits. The original reader discussion specifically notes the need to recheck a more specific style after changing its parent.
Our experiment applied effective flags directly to isolate layout behavior. It did not reproduce the reader's style hierarchy, numbered-list structure or original redacted file.
Check that the intended group can physically fit
Our heading and following detail were short enough to fit together on one page. The test does not show that a pair containing very long paragraphs, large spacing or embedded objects can fit within another document's printable area.
Check page size, margins, paragraph spacing and the actual group height before expecting a keep setting to solve the layout. A whole chain that is taller than the page cannot be made to fit merely by marking every link.
When you deliberately need a new page for a structural reason, use an intentional page-break rule at an appropriate location and inspect its effect. Do not add blank spacer paragraphs simply to push one item down without understanding the connected content.
Verify the saved result
Compare the intended heading and first detail after the change, then inspect neighboring pages for newly stranded items or unexpected gaps. Save the working copy, reopen it and review the relevant page boundaries before replacing the source document.
We tested LibreOffice 26.8.2.2 on macOS 27.2 arm64 through native paragraph properties, PDF layout and page-position inspection. The exact page numbers above belong only to that fixture. We did not click the graphical paragraph dialog or establish a universal page-breaking algorithm, an official bug diagnosis, or a fixed release for the reader's document.