Quote:
Originally Posted by kovidgoyal
There is no different engine. All rendering is handled by the browser engine. The browser engine can always decide to ignore break-inside if they feel like it. The only place this can be fixed is the browser engine. And it cannot in principle ever be fixed absolutely, since if the content in the block marked with break-inside is larger than the available space, it HAS to be broken up.
|
Then I cannot get it how Calibre-Web and Calibre E-book viewer share the same browser engine but Calibre-Web faced with tall images in the block handles it properly to fit this whole block on one page even sometimes adding additional content (see screenshot) of the book on this page but Calibre E-book viewer breaks content consistency?
Definitely there have to be differences in how they handle content and therefore between their code. My main field of interest in IT is investigating bugs in software or hardware consequently I mainly use Assebmler in my hobby work but, IMHO, the algorithm of finding and fixing in the code still the same in both using Assembler and Python.