Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Chromium is not categorically unable to paginate a column flexbox. The CSS Flexible Box Layout specification permits breaks between flex items and inside them, but it does not define the exact layout of every fragmented flex container. If printing skips or misplaces a break, the cause depends on the page’s markup, sizing, break rules, and Chromium version.
What the CSS rules allow
The W3C’s CSS Flexible Box Layout Module Level 1, “Fragmenting Flex Layout” says: “Flex containers can break across pages between items, between lines of items (in multi-line mode), and inside items.” For a column flex container, the specification distinguishes breaks at item boundaries from breaks within items. It also says that a forced break inside one flex item does not force a break inside its siblings.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
ASUS 2020 Chromebook 15.6 Inch Non-Touch Laptop, Intel Celeron N3350 up to 2.4 GHz, 4GB LPDDR4 RAM,... | $279.00 | Buy on Amazon |
There is an important limit: the specification says the exact layout of a fragmented flex container is not defined at this level. It describes break behavior, but does not promise an identical result for every combination of flex sizing, alignment, and page fragmentation. So a particular Chromium failure should be treated as a reproducible browser-layout problem, not evidence that column flexboxes can never break across pages.
Check what the break rules are asking Chromium to do
break-inside controls whether a page, column, or region break is allowed inside a generated box. Values such as avoid express a preference against a break inside that box; avoid-page targets page breaks. These properties are not universal pagination repairs: an avoid rule may make an item harder to fit, and it does not guarantee that a flex container will fragment as intended.
page-break-inside is a legacy compatibility alias for break-inside; its auto and avoid values map to the corresponding modern values. Use the property that matches your intended break behavior, then verify the result in the same document and output path that fails.
Reduce the failure to a reproducible example
Before changing the layout, record the exact Chromium build, how you produce the pages, and where the actual breaks differ from the expected breaks. A concise reproduction helps distinguish a flex fragmentation issue from a print-path or sizing interaction.
- Make a minimal HTML and CSS example containing the column flex container and the fewest items that still reproduce the problem.
- Record the full Chromium version and whether you use print preview, print-to-PDF, or headless PDF generation. Also record page dimensions and relevant print settings.
- Describe the expected break location and what actually happens, such as an item staying together, content being cut off, or a later item moving unexpectedly.
- In the reproduction, check whether the flex container is single-line or multi-line, whether its main-axis size is definite, and whether items fit in the remaining page space.
- Inspect
break-inside,break-before, andbreak-afteron both the container and its items. The specification treats breaks at different flex-item boundaries differently.
Isolate sizing and nesting interactions
Once the minimal case is stable, remove one potentially interacting feature at a time: nested flex containers, percentage heights, fixed heights, overflow constraints, and break-inside: avoid. Re-test after each change, keeping the same Chromium build and PDF or print method. If removing one feature changes the break behavior, you have a more useful lead than a broad rule such as “flexbox does not paginate.”
Recommended Free Tools
A related report, Chromium issue 365922171, describes a nested-flex and percentage-height interaction when printing to PDF, with a reproduction using Chromium 127.0.6533.99. It is relevant context, not proof of the cause of another page-break failure: the reported scenario is specific, and the issue does not establish that it matches your case or that a fix has shipped.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Compare a block-flow print layout if flex fragmentation remains unreliable
If item-level pagination is essential and the reduced flex example still fails, compare it with a simpler block-flow layout for print. Treat that as a diagnostic option, not a guaranteed fix: test the alternative in the affected document and Chromium version before adopting it. Keep the comparison focused on the variables that matter—flat versus nested structure, break rules, sizing constraints, and the exact output path.
Chromium’s RenderingNG fragmentation deep-dive provides historical engine context: its description of the legacy engine says that it had no flex or grid fragmentation support. That architectural history alone does not characterize current Chromium behavior, so it cannot settle a present-day reproduction.
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.
Free tools Windows power users keep installed
One-click scans. No signup required.
