View Single Post
Old 10-28-2014, 12:00 AM   #5
AlexBell
Wizard
AlexBell ought to be getting tired of karma fortunes by now.AlexBell ought to be getting tired of karma fortunes by now.AlexBell ought to be getting tired of karma fortunes by now.AlexBell ought to be getting tired of karma fortunes by now.AlexBell ought to be getting tired of karma fortunes by now.AlexBell ought to be getting tired of karma fortunes by now.AlexBell ought to be getting tired of karma fortunes by now.AlexBell ought to be getting tired of karma fortunes by now.AlexBell ought to be getting tired of karma fortunes by now.AlexBell ought to be getting tired of karma fortunes by now.AlexBell ought to be getting tired of karma fortunes by now.
 
AlexBell's Avatar
 
Posts: 3,413
Karma: 13369310
Join Date: May 2008
Location: Launceston, Tasmania
Device: Sony PRS T3, Kobo Glo, Kindle Touch, iPad, Samsung SB 2 tablet
Quote:
Originally Posted by kguil View Post
I don't know of one that would have the same effect. I'd actually welcome and feedback I can get about this. This is the problem: for any non-trivial amount of text setting the following:

webkitColumnBreakAfter='always', and webkitColumnBreakBefore='always'

...makes everything incredibly slow.

Note that I'm apply these iff pageBreakAfter and pageBreakBefore are set.
I'm sorry, I don't understand.

I generally use page break before to start a new 'chapter' in a short story.

The CSS is:

.portion { page-break-before:always;
text-indent:0;
text-align:center;
font-size:138%;
margin:0; padding:20px 0 10px 0;}
p.portion+p {text-indent:0; }

and the HTML is something like:

<p class="portion">Chapter 2</p>

Is this what you mean?
AlexBell is offline   Reply With Quote