Bug 35787 - Getting warning about 'maximum constraint in block-progression-dimension'
Summary: Getting warning about 'maximum constraint in block-progression-dimension'
Status: CLOSED FIXED
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: page-master/layout (show other bugs)
Version: trunk
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-19 04:49 UTC by Nils Meier
Modified: 2012-04-01 07:13 UTC (History)
0 users


Attachments
Input FO that is being send to FOP (21.35 KB, text/xml)
2005-07-19 04:50 UTC, Nils Meier 		Details
1.0dev output after getting warnings on STDERR (19.16 KB, application/pdf)
2005-07-19 04:51 UTC, Nils Meier 		Details
output with maint branch (looks slightly different) (1.25 KB, application/pdf)
2005-07-19 04:51 UTC, Nils Meier 		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 Nils Meier 2005-07-19 04:49:39 UTC 
See attached - a fairly simple .fo that i hand off to last nights
code in trunk. I'm seeing the following error on STDERR about
a dozen times which does not show up with the maintenance branch:

18.07.2005 22:46:55 org.apache.fop.layoutmgr.table.TableContentLayoutManager
createElementsForRowGroup
Contents of row 0 violate a maximum constraint in block-progression-dimension.
Due to its contents the row grows to 14250 millipoints. The row constraint
resolve to MinOptMax: min=14000; opt=14000; max=14000
Comment 1 Nils Meier 2005-07-19 04:50:52 UTC 
Created attachment 15700 [details]
Input FO that is being send to FOP
Comment 2 Nils Meier 2005-07-19 04:51:19 UTC 
Created attachment 15701 [details]
1.0dev output after getting warnings on STDERR
Comment 3 Nils Meier 2005-07-19 04:51:38 UTC 
Created attachment 15702 [details]
output with maint branch (looks slightly different)
Comment 4 Jeremias Maerki 2005-07-19 15:03:17 UTC 
Another good one, Nils, although it took me a little to find out what was 
wrong. Here we go: The FO file creates tables with collapsing border model 
(which is the default, but not fully implemented, yet. See warnings). Now the 
code that produces the warning message you describe doesn't take into account 
that the height property only applies to the table cell's content. The border 
widths must not be taken into calculation whether the content is taller than 
allowed. But that's exactly what happens right now. So, yet another things to 
look at for me. Thanks, Nils!
Comment 5 Jeremias Maerki 2005-07-19 16:07:53 UTC 
I think the problem should be fixed now.
http://svn.apache.org/viewcvs?rev=219685&view=rev
Comment 6 Glenn Adams 2012-04-01 07:13:20 UTC 
batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed