View Single Post
Old 11-30-2015, 05:30 PM   #6
dgatwood
Curmudgeon
dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.
 
dgatwood's Avatar
 
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
Quote:
Originally Posted by 1v4n0 View Post
Well what surprised me is that the kindle skipped the html file altogether, but only if the first <p> had absolute positioning (or maybe it's because it can only tolerate one "absolutely-positioned" item per file?)

Also, the positioning for the image at the bottom does in fact work.

As for KF7 vs KF8, I don't know what you're talking about

This is an AZW3 I got from an EPUB I did, via calibre conversion.

TY all.
Ah. I should have read your original post more carefully. You probably shouldn't use absolute positioning in the way you're using it, because it isn't relative to an enclosing element.

You can safely use absolute positioning on elements that are inside any enclosing element that is positioned in a non-fixed manner. Just don't use absolute positioning on elements whose ancestors are all position:fixed (the default).

This is probably a bug in whatever version of WebKitGTK Amazon branched from.
dgatwood is offline   Reply With Quote