Bug 43815 - If Block Container doesn't have width/height properties then strange effects can occur on layout of child elements
Summary: If Block Container doesn't have width/height properties then strange effects ...
Status: CLOSED FIXED
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: general (show other bugs)
Version: trunk
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-08 09:05 UTC by Chris Bowditch
Modified: 2012-04-01 06:40 UTC (History)
0 users


Attachments
FO to reproduce problem (2.48 KB, text/plain)
2007-11-08 09:06 UTC, Chris Bowditch 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Bowditch 2007-11-08 09:05:24 UTC 
If you run the attached FO file you will see that the text does not line up 
with the bullet points on the left. The structure of the FO files is quite 
starnge because a mixture of tables and list blocks are used to achieve what 
could probably be achieved with a straight list. Still the FO is valid and my 
customer asked why the bullet does not line up with the text. The list blocks 
and table are children of a block-container which has position="absolute" but 
does not have width/height properties specified. If the width/height 
properties are added then the bullet points then line up with the text! So our 
BC LM must expect width/height and if they are not specified it can cause 
strange layout effects on the child LMs.
Comment 1 Chris Bowditch 2007-11-08 09:06:43 UTC 
Created attachment 21096 [details]
FO to reproduce problem
Comment 2 Andreas L. Delmelle 2008-05-04 22:46:35 UTC 
FWIW: bug seems to be fixed in current FOP trunk (probably also 0.95).

I suspect the issue has been fixed with Jeremias' refactoring of BlockViewport handling...

Chris, can you confirm, so that we may close this one?
Comment 3 Chris Bowditch 2008-05-06 04:48:16 UTC 
Thanks everyone - this bug is fixed!
Comment 4 Glenn Adams 2012-04-01 06:40:00 UTC 
batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed