From d324cc1917bd595f9e5fb9ef7e14c94fd5db27d1 Mon Sep 17 00:00:00 2001 From: Jeremias Maerki Date: Thu, 15 Dec 2005 16:59:37 +0000 Subject: Bugzilla #37875: Some content inside a table-header may not have been renderered on pages n > 1 in certain conditions. LineLM kept state between calls to addAreas which can have ugly side-effects in case of table-headers, for example, where the same positions are rendered more than once. I don't know why the bug only manifests if there's an overflow in the second line of the table-header in the test case. git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@357045 13f79535-47bb-0310-9956-ffa450edef68 --- .../standard-testcases/table-header_bug37875.xml | 76 ++++++++++++++++++++++ 1 file changed, 76 insertions(+) create mode 100644 test/layoutengine/standard-testcases/table-header_bug37875.xml (limited to 'test') diff --git a/test/layoutengine/standard-testcases/table-header_bug37875.xml b/test/layoutengine/standard-testcases/table-header_bug37875.xml new file mode 100644 index 000000000..d25dd6ae3 --- /dev/null +++ b/test/layoutengine/standard-testcases/table-header_bug37875.xml @@ -0,0 +1,76 @@ + + + + + +

+ This test checks Bugzilla #37875: Content in a table-header is not completely painted on subsequent pages, but only + if a line in the header overflows in inline-progression-direction. +

+
+ + + + + + + + + + + + + + + Blah-blahblah + + + + + + + 1 + + + + + 2 + + + + + 3 + + + + + 4 + + + + + + + + + + + + + + +
-- cgit v1.2.3