Quote:
Originally Posted by JSWolf
If you choose Unset, do the margins set in CSS take effect?
|
This is where the real weird shit starts to happen: between p-tags still no margins, but between p and div the margin gets applied. The only issue, I almost have no p among divs where that would show up, only at some seldom placed vignettes, thus I've never encountered that behavior before. Anyhow, the most important application for p-tag margins is between p-tags. This is just no normal behavior.
And: the page margins get set at a level between small and standard. Since I'd consider that not beautiful I'd had to set these margins as well with the result that other readers might look crap. So as a solution I would have to apply body margins via JavaScript, that's just an overkill of precalculation for most of the readers which will then take even more time to start presenting the pages.
And let's be honest: most of the people will have margins set (by default they are set to standard) and never come up with the idea to unset them so that they can see nicer displayed vignettes (besides the fact that I'd have to include a manual about the how and what and why so that they'd even know about this crap).
Quote:
Originally Posted by JSWolf
It effects nooks, Sony Readers and ALL Kobo Readers because Kobo use an older version of RMSDK and you cannot be sure if the eBooks will be read as ePub (RMSDK) or KePub (ePub3 compatible), you have to code as though they will be read with RMSDK.
|
But with what result, will the :before and :after styles simply get ignored or do there serios things happen?