Free tools Windows power users keep installed
One-click scans. No signup required.
Chromium treats break-inside: avoid on a table section as a real break-avoidance constraint—not something to ignore—but it cannot keep content together when its size or available page space makes that impractical. For printed tables, use semantic row groups, apply avoidance only where it helps, and check the print preview or PDF in the browser and print setup you intend to support.
How Chromium handles table breaks
Printing splits a document into pages, a form of CSS fragmentation in which each page is a fragmentainer. Chromium’s LayoutNG block-fragmentation work initially shipped in Chrome 102; that engine background helps explain the model, but the more specific evidence about table sections comes from a Chromium source change dated February 11, 2026.
As an Amazon Associate I earn from qualifying purchases.
That change corrected the expected result for a print test: the prior expectation said break-inside: avoid on a table section should be disregarded, and the commit says that expectation was wrong. Chromium added a reference test and corrected the expectation. This shows that the section’s avoidance constraint matters to layout; it is not a guarantee for every table configuration or print environment. Chromium source change, February 11, 2026. The Chromium commit URL is not available in the cited source details here, so no link is supplied.
Use break-inside to request that content stay together
break-inside is the current CSS property for controlling breaks within an element. Its avoid value asks the layout engine to avoid a break inside that element. The older page-break-inside property is retained as a legacy alias for compatibility. These properties express a constraint, not an unconditional promise that content will fit on a page.
#1 Best Overall
The CSS Fragmentation specification defines break-inside in the context of fragmentation, including page-specific avoidance values. CSS 2.1 describes page-break-inside: avoid as avoiding a page break and allows user agents to apply page-break properties to table rows. W3C CSS Fragmentation Module Level 4, MDN: break-inside, and W3C CSS 2.1 paged media.
Choose the scope of break avoidance
For ordinary data tables, put column headings in <thead> and data rows in <tbody>. Apply avoidance narrowly to rows or row groups that should remain intact for comprehension; imposing it on a whole long table may constrain layout without solving the underlying space problem.
- Individual row: Useful when splitting a row would make its contents hard to read. A row taller than a page cannot be kept intact on that page.
- Row group or table section: Chromium’s February 2026 test correction indicates that an avoidance constraint on a section matters. A group still needs to fit within the available space to remain together.
- Whole table: Usually too broad for a table that spans pages. It can make the layout constraint impossible to satisfy when the table is longer than the available page area.
A practical starting point is:
@media print {
thead { display: table-header-group; }
tfoot { display: table-footer-group; }
tr { break-inside: avoid; page-break-inside: avoid; }
}The explicit header and footer display values express conventional print intent. They do not ensure identical results in every Chromium version, operating system, or PDF and printer pipeline. The table specification sets conditions for repeating headers and footers rather than making repetition unconditional. W3C CSS Table Module Level 3.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →When table headers and footers repeat
The CSS Table Module Level 3 describes when header and footer rows must repeat across pages spanned by a table. Its conditions include the page being the table’s fragmentainer, the header or footer having break avoidance, the group’s height staying within the specified limits (up to one quarter of the page height for each), and repetition not causing a row to appear twice on the same page. The specification permits browsers to extend repetition to other fragmentation contexts, such as columns, but does not require that extension. Check the rendered output rather than assuming every table setup will repeat its headings.
Why an avoided break may still happen
avoid asks the browser to keep content together when layout allows; it does not create additional page space. A row or group that is too tall for the available area cannot be made to fit intact simply by adding the property. A table starting near the bottom of a page may also have too little remaining space for a row or group, so the outcome depends on the layout and the content’s dimensions.
Print settings also affect the space available. Page size, margins, scale, and browser-generated headers and footers can reduce or change the printable area. Chrome’s documentation says CSS margin-box content became available in Chrome 131 and explains that automatic browser headers and footers may be turned off in the print dialog. Chrome for Developers: print margin boxes and page layout.
Rank #4
Validate the actual print or PDF output
Check both print preview and the resulting PDF using the Chromium version and environment you need to support. Include a short row, one nearly as tall as a page, one taller than a page, and a table that begins near the bottom of a page. Repeat the check with the intended paper size, margins, scale, and browser header/footer setting. This reveals whether the chosen constraints improve the specific output; it is a validation procedure, not a claim that these cases have been tested across all Chromium environments.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteFor engine context, Chrome’s LayoutNG fragmentation explanation describes printing as fragmentation across pages. Chrome for Developers: LayoutNG fragmentation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
