View Single Post
Old 08-26-2023, 01:21 PM   #1403
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 jhowell View Post
Those wishing to use negative margins in order to fit more text on the screen should be aware that doing so is unsupported by Amazon and can trigger bugs in the Kindle reading software.
A weirdness I haven't bothered to post is that a negative margin on the html element and a table on a page are just fine...until you add in a drop cap.

This results in the rendering seen in the first attached picture, where the drop cap floats to where it belongs, but the text doesn't flow around it.

Also, even without negative margins at the html level, there are other combinations of CSS that cause the left margin to be farther left than the CSS would indicate. One of these cases seems to be the same as the "margin at the top of the page" bug, where it isn't rendered correctly until something non-blank is rendered. I've also seen it in

And, the Kindle renderer in general doesn't support negative margins that push content outside the enclosing block. This is perfectly legal, and has actual uses (like hanging initial punctuation outside the text block), although they are rare.
Attached Images
 
nabsltd is offline   Reply With Quote