DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38054>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38054


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO




------- Additional Comments From [EMAIL PROTECTED]  2006-01-09 10:17 -------
Matt, I've had a look at your test case. I must say that I can't determine with
100% confidence what you're trying to show. I've found one problem with your
test case: Running your test case unmodified causes the span="all" block to be
ignored. The problem here is that the negative space-before is larger than the
positive height by the height of the single line of text and the space-after
added together (-18pt + 12pt + 2.5pt = -3.5pt). There is some code in the area
tree that causes a span area with a negative height to be removed. This seems
wrong. I'm going to change that.

As for the other cases you describe, I can't reproduce them. A negative
space-before with conditionality="retain" on a block after a block with
span="all" works just fine (your point 1). On your point 2, I can only say that
your test case is a little weird, since the lines "HeaderText1" etc. have a huge
start-indent. Your text in the first block is indeed balanced to two columns
(which is correct). HeaderText lines 3 to 6 are not visible as they have a
start-indent that places them outside the main reference area (even outside the
page) for the second column.

I'd like to suggest you revise your test case again, maybe try to simplify it.
What's often helpful to determine problems is using background-color on
region-body and blocks to see which area is taken up exactly by the various
elements. Also, set overflow to "visible" while looking for problems. As an
advanced means you can have a look at the output of the area tree XML output
(-at on the command-line). It can give you an indicator whether some parts have
been ignored/discarded or if they are painted but offset so they are not 
visible.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to