Quote:
Originally Posted by JSWolf
Quote:
Originally Posted by Turtle91
h3 + p, p.SceneBreak + p, div.ChapterDivision + p {text-indent:0; margin-top 2em}
All works fine for me. However, don't forget to check that your target device/app supports this kind of standard styling...
|
For a scene break,you don't want to use a margin-top. It doesn't work. When you have the space at the end of the page, the space gets lost. Use padding-top: 2em; as the space is not lost.
Instead of using just space or a graphic or * * * (looks awful), I use an <hr/>. The following code and it works very well.
Code:
hr {
margin-top: 1em;
margin-right: 40%;
margin-bottom: 0.9em;
margin-left: 40%;
border-top: 2px solid;
}
Baen books does something I find just plain wrong. They indent the first paragraph of a chapter and the paragraph after a scene break. This is something I really dislike.
Then there are the books that don't indent the paragraph after some offset text. Again that just looks wrong because this is not a new scene.
|
Jon -
Please don't take a 1.5 year old post out of context...it confuses people. Also, you missed the point of my post
again. The post was to say that
multiple selectors, separated by a comma, worked fine in all the devices I have tried. It was not to get back to your personal preference about using padding instead of margin.
OBTW - just to point out - you are arguing to use padding-top instead of margin-top, but then your example <hr> uses margin....
If anyone cares, there are several images that show how padding gives extra space at the top of a page, vs. margin, which doesn't. Some people may want that space at the top of a page, some may not. Some may just prefer an asterism or a fleur. (hey that rhymed

) It is up to the author/publisher to determine which css they wish to use...
that thread goes into greater detail about the pros/cons of margin vs. padding vs. asterisms for section breaks.