It's right that the descendants of static-content should not be broken,
but using the breaker allows to make use of the stretch/shrink
functionality (min/opt/max stuff) without having to write extra
duplicate code just for static content.
On 05.06.2008 13:27:36 Vincent Hennebert wrote:
> Does anyone know why does StaticContentLM implement its own breaker
> (StaticContentBreaker) and breaks its content using the
> PageBreakingAlgorithm? AFAIK descendants of a static-content element are
> not supposed to be broken over several pages.