View Single Post
Old 04-18-2020, 10:04 PM   #33
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,195
Karma: 27110894
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
This endless arguing is pointless. NO BROWSER, chromium included, will ever resize content to honor break inside. Which means that by its very nature it is ADVISORY since there is never any guarantee that content will fit in the viewport. You as an author can attempt to do that by using viewport units for image sizes. Set your image height to 75vh for instance. Then assuming the viewport is large enough that 25vh provides enough space for the text they will not be split.

*All* that break inside guarantees is, that if the block is not at the top of the column/page and does not fit on the page it will be pushed to the next column/page. Chromium could well be buggy in implementing even that, but that changes nothing. If the block is too large to fit on even an empty page, IT WILL BE BROKEN UP. Therefore, THE PROPERTY IS ADVISORY.

And you really need to go argue with browser developers about this properties semantics.
kovidgoyal is online now