Heading page-break-after not working

[Graham Campbell]

I have set the Page Break After property in each of my heading styles (H1 to H6, as well as a couple of classes of H1) to Avoid, yet Flare only occasionally sets the correct behaviour in the PDF output. The rest of the time I get this:

break-after.png

That shows my H2 and H3 styles, with the break added immediately after my H2 - precisely what I don't want.

Also, in the same project, I have set the H1 headings to always break before - basically ensuring that new top-level sections always start on a new page. However, that never works and I'm sometimes left with content like this:

not-breaking-before.png

That shows an H1 immediately followed by an H2 right at the bottom of the page.

I define the heading styles in one stylesheet only, so there is no way I can see of there being a cascade/inheritance conflict.

Any input would be appreciated.

G

[forfear]

is it possible you have h2 tag defined twice in the same stylesheet in the same medium, since you are pretty sure the cascading effect is not the issue.

Code: Select all

h2{
some page break code
}
....
h2{
another page break value setting
}

i am not sure but good to check.

[Graham Campbell]

It's defined once only, but you're right - it is good to check these basic things.

G

[forfear]

still not working?

[Graham Campbell]

Still not working.

None of my heading styles comply with this, whereas other paragraph styles do (such as the titles of procedures or Note and Important boxes).

Quite confused about this one. page-break-after: always; does work. page-break-before: always; also works. page-break-after: avoid; never works for H1, H2 etc.

I'd still appreciate any suggestions on this one if anyone's still reading!

[LTinker68]

I vaguely recall at one point there being a bug with one of the page-break options. Don't remember if it was that one, or if it was supposedly fixed. You can submit a bug report to MadCap and they'll indicate if they can recreate it. They might even indicate if it's a known bug.

[Graham Campbell]

In the meantime since I last visited this thread, I've been rebuilding our in-house CSS and as a result I no longer experience this problem.

I can only conclude that our original stylesheets (which were over three years old and quite bloated by the time I came to use them) were conflicting in some way to cause the problem.

Not sure I'll ever know what it was, but thanks to everyone for replying just the same!

G