View Single Post
Old 07-26-2023, 10:13 AM   #18
nabsltd
Fanatic
nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.
 
Posts: 528
Karma: 9529956
Join Date: Aug 2013
Location: Hamden, CT
Device: Kindle Paperwhite (11th gen), Scribe, Kindle 4 Touch
Quote:
Originally Posted by Quoth View Post
Crazy.
Even crazier because it doesn't always create the space the author intended.

Kindles have a bug where it won't render space (margins, padding, etc.) correctly at the start of the HTML file (chapter start, etc.), and also incorrectly collapses anything rendered as blank space (like &nbsp along with actual whitespace.

It's likely caused by not special casing the "don't show blank space at the top of the screen on page turn" logic. This makes sure that if something like a scene break paragraph starts at the top of the screen, the blank space isn't needlessly rendered. That is a case where you do want to treat   as if it was actual whitespace.

The workaround is to put a paragraph at the top of the page, and put content with visibility: hidden; styling.
nabsltd is offline   Reply With Quote