Page break before image

[Jugen]

Currently if there isn't enough space at the bottom of a page for an image then a page break is inserted and the image is placed on the next page. This is great and probably the expected behavior most of the time. :-)

Is there a way though from preventing this from happening ?
In certain cases I would like the image to be placed even if there isn't enough space, with the remaining part of the image either dropped, or to overflow onto the next page.

If there isn't already a way to do this could the css style overflow: hidden/visible maybe be extended to be able to accommodate this ?

[Jugen]

After some debugging I've managed to modify LineBox.checkPagePosition to implement the above behavior with the following code:

if ( needsPageBreak && ! alwaysBreak && getStyle().isBlockEquivalent() )
{
    CalculatedStyle  parentStyle = getParent().getStyle();

    if ( parentStyle.isAutoHeight() && parentStyle.getIdent( CSSName.OVERFLOW ) == IdentValue.HIDDEN )
    {
	setHeight( Math.max( 0, pageBox.getBottom() - c.getExtraSpaceBottom() - getAbsY() ) );
	needsPageBreak = false;
    }
}

[Jugen]

@danfickle suggested trying -fs-page-break-min-height: 100px; (Thanks dan)

Unfortunately -fs-page-break-min-height doesn't work on images, I tried:

<div style="-fs-page-break-min-height: 100px;">
   <img .... />
</div>

[danfickle]

Hi @Jugen

Thanks for persevering with this issue.

I wrote some tests around this problem and discovered that the generic problem is that there is no way to specify that inline-block elements can split between pages. A possible workaround is to use block for images that you want split capable:

img {
  display: block;
}

P.S Unlike my previous suggestion I have tested that this works.

[Jugen]

@danfickle Thank you very much for the time you've put into this issue, I really appreciate it !

I'm not a CSS or HTML expert but I think that using display: block on images that you don't mind overflowing across pages is acceptable. Maybe its just not intuitive (?), but then that's what we have docs for :-)