Bugzilla

(In reply to Daniel Holbert [:dholbert] from comment #1)
> For the record, here's a list of containers which (when taller than a page) will cause us to trigger this "slicing" fragmentation-fallback behavior, which potentially results in slicing-text-in-half at pagebreaks:
> (1) Elements with `display: inline-block`, `inline-table`, `inline-grid,` `inline-flex`.

Here's a testcase for this category. As it turns out, Chrome actually slices text at pagebreaks for this category, too. (E.g. on my system, Chrome print-previews this testcase with some text split between page 1 and 2.)

(In reply to Daniel Holbert [:dholbert] from comment #1)
> For the record, here's a list of containers which (when taller than a page) will cause us to trigger this "slicing" fragmentation-fallback behavior, which potentially results in slicing-text-in-half at pagebreaks:
> (1) Elements with `display: inline-block`, `inline-table`, `inline-grid,` `inline-flex`.

Here's a testcase for this category. As it turns out, Chrome actually slices text at pagebreaks for this category, just like Firefox does. (E.g. on my system, Chrome print-previews this testcase with some text split between page 1 and 2.)

(In reply to Daniel Holbert [:dholbert] from comment #1)
> For the record, here's a list of containers which (when taller than a page) will cause us to trigger this "slicing" fragmentation-fallback behavior, which potentially results in slicing-text-in-half at pagebreaks:
> (1) Elements with `display: inline-block`, `inline-table`, `inline-grid,` `inline-flex`.

Here's a testcase for this category. As it turns out, Chrome actually slices text at pagebreaks for this category, just like Firefox does. (E.g. on my system, Chrome print-previews this testcase with some text split between page 1 and 2. That might vary depending on font / page size / etc, but if you scroll through the pages, you should see *some* pagebreak where text is split across pages, in both Chrome and Firefox.)