Quote:
Originally Posted by bookman156
That's precisely where you should use padding or you risk having your margin space overwritten simply because someone slightly changes the all-round page margin in their ereader. It seems to vary between ereaders, altering the page margin on the Lithium Reader in Android leaves your own other special margins intact, for example, but not in PocketBook Reader. Padding sidesteps the issue. In epubs I only use margin now for page margin (0.5em), setting to zero on the p tag, and in a transitional hr tag:
Code:
hr.transition {
margin: 1.5em 40% 1.55em 40%;
border: 0;
border-bottom: 1px solid darksalmon;
}
|
Your 1.5em top/bottom margins are too large. That would make it slightly more then 3em. Too large for a section break. You want something like 0.9em top/bottom margins. Also, you should be making that line 2px as 1px can be a bit too thin on a 300dpi eInk screen. Also, darksalmon is a bad idea for eInk screens. Leave the line at the default color of black.
As for padding, you don't need it just in case someone decides to change the L/R margins. That is handle properly. I know Kobo handles it properly. As for @page, get rid of it. It's not needed. Don't monkey with the margins. Let us set our margins. As for padding, it's best used for a section break where you are just using blank space. Otherwise, there's very little need to use padding.