When he block following the absolutely positioned block-container has space-before property defined, this property applies and the (second) block is shifted down from the block-container. Comments from Jeremias Maerki (fop-user list): Indeed, the BlockContainerLayoutManager creates a KnuthBox (w=0) in the element list for the absolutely positioned block-container which is currently interpreted by the SpaceResolver as a fence. And a fence makes the SpaceResolver believe that there's content before the space. Looks like we should find a solution to indicate to the SpaceResolver which boxes are no fences. Another example would be the often-used empty block at the end of the flow for "page x of y" which probably creates a fence, too.
code snippet: <fo:flow font-family="Times" font-size="12pt" flow-name="xsl-region-body" margin-left="1.37in"> <fo:block-container margin="0pt" padding="0pt" width="30pt" start-indent="0pt" absolute-position="absolute"> <fo:block>[abs]</fo:block> </fo:block-container> <fo:block space-before="9pt">lorem ipsum dolores...</fo:block> </fo:flow>
Created attachment 18559 [details] fo source to run example
Created attachment 18560 [details] output with absolutely positioned block-container
Created attachment 18561 [details] output with no absolutely positioned block-container
resetting P2 open bugs to P3 pending further review