I think, universal pagination will always be a problem, because of varying paper formats, etc. However, there's the `break-` suite of CSS rules (`break-before`,

I think, universal pagination will always be a problem, because of varying paper formats, etc. However, there's the `break-` suite of CSS rules (`break-before`, `break-inside`, `break-after`, formerly `page-break-before`, etc) to handle the worst cases, like cutting through images, lists, or vital portions of text. But these rules are more about what is to be avoided and not so much about how it should be done. A somewhat mundane reason for the examples, you provided, and for these rules seldom seen in action may be that with websites, there's rarely substantial care invested in print layouts, anymore. (This used to be slightly different, when executives still used to interact with the Internet on a print-out-only basis and pages came with extensive, dedicated print style-sheets. Meaning, print was how your customers were probably experiencing their new website, as were their peers, so it was important. There are also possible, additional problems related to reflow and varying resources, esp. with JS-generated content.) In a way, "mobile first" also meant "print definitely last", since it's yet another layout to maintain. [1] https://developer.mozilla.org/en-US/docs/Web/CSS/break-before https://developer.mozilla.org/en-US/docs/Web/CSS/break-befor..., https://developer.mozilla.org/en-US/docs/Web/CSS/break-after https://developer.mozilla.org/en-US/docs/Web/CSS/break-after, https://developer.mozilla.org/en-US/docs/Web/CSS/break-inside https://developer.mozilla.org/en-US/docs/Web/CSS/break-insid...