Quote:
Originally Posted by kguil
I suspect it is related to a (known) issue of how WebKit "balances" columns. Could you email me at support to try and reproduce this? - hopefully, I'll be able to fix it.
|
Ah,
webkit issue
thanks for the pointer.
Indeed, now that I payed some more attention to this I see it affects just about every e-reader supporting multiple columns.
As I suspected
fixed.
:first-child nicely takes care of that so no need to go waste time on this one
thanks just the same for the willingness to look into it
-------------
EDIT: Come to think of it, webkit is not to blame. It's doing exactly what it was told to do. That's what you get when thinking in 'pages' too much. You tend to forget that an e-Reader is basically still a browser, so even if it is forced to display in more than one column, the first element (in this case either the body or a content container) at the top of a logical page is still only going to be :first-child when it is the first element (with regard to its parent element of course) in a single html file loaded from the e-book. Every next 'page' is just a view-port over the remaining part of the file. removing a top margin (if it has one) from the content container would likely have the same result.