View Single Post
Old 06-18-2025, 05:52 AM   #21
Quoth
Still reading
Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.
 
Quoth's Avatar
 
Posts: 14,547
Karma: 108666825
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper
Quote:
Originally Posted by Falkor View Post

Getting page breaks to work across all reading applications is a pain, though. The order in which the different css properties are arranged matters – and the order that works in Thorium and ADE doesn't work in Books... although maybe I'm missing some crucial detail to make it work. )
A new HTML file always starts at the top of the screen. (epubs converted to old mobi KF7, azw3/KF8 and KFX by Amazon or locally, and any epub renderer doing pages not continuous scrolling)
In such a case "padding-top: <value>em;" seems to always work for the first item, while some renders will remove margin-top at start of a screen and some may remove margin-bottom at the bottom of the screen.

Don't use any webkit or adobe or media queries if you want 100% compatibility, because even "fall back" code might fail.
Quoth is offline   Reply With Quote