View Single Post
Old 07-05-2025, 03:49 PM   #23
RbnJrg
Wizard
RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.
 
Posts: 1,801
Karma: 8700631
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
Quote:
Originally Posted by ElMiko View Post
THIS is the explanation I was looking for. Thank you for articulating it so clearly!

Does this mean that two adjacent "inline-block" <p> elements will also want to run together?
Yes, they will. And if they are at the end of the page, and the user increases the font-size, the text inside the blocks won't break; both blocks will go to the next page. It won't have part of the text at the end of the page and part of the text at the start of the next page; all the text will remain joined.

With the floating method you can have similar results if you add the properties "page-break-inside: avoid", "break-inside: avoid" and "-webkit-column-break-inside: avoid" but all these properties are implicit in inlined blocks. But with one caveat: while the "display: inline-block" property is supported by virtually all e-readers (including ADE), the "page-break-inside: avoid," "break-inside: avoid," and "-webkit-column-break-inside: avoid" properties are not supported by all e-readers.

Last edited by RbnJrg; 07-05-2025 at 03:57 PM.
RbnJrg is offline   Reply With Quote