Issue 74281 - Table from sub doc not correctly seperated in master doc
Summary: Table from sub doc not correctly seperated in master doc
Status: CLOSED DUPLICATE of issue 43411
Alias: None
Product: Writer
Classification: Application
Component: formatting (show other issues)
Version: OOo 2.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
Depends on:
Reported: 2007-02-07 15:58 UTC by rbos
Modified: 2007-02-09 09:57 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Master document to show the problem (10.80 KB, application/vnd.oasis.opendocument.text)
2007-02-07 15:59 UTC, rbos
no flags Details
Sub document to show the issue (11.91 KB, application/vnd.sun.xml.writer)
2007-02-07 16:00 UTC, rbos
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description rbos 2007-02-07 15:58:45 UTC
A table is not finished correctly in a master document with footers when the
table just fits on a page in a sub document (without footers).  A part of the
table is hidden behind the footer.  Hopefully the attached master document and
sub document shows the issue clearly.

- Open the master document
- Say yes to update links
- Go to page 4 and discover that step 15 is missing (14 is only shown partly).

The same table is shown correctly in the sub document...
When the header and the footer are switch off, the table is shown correctly.
Comment 1 rbos 2007-02-07 15:59:38 UTC
Created attachment 42830 [details]
Master document to show the problem
Comment 2 rbos 2007-02-07 16:00:08 UTC
Created attachment 42831 [details]
Sub document to show the issue
Comment 3 kpalagin 2007-02-07 21:45:20 UTC
Confirming with 2.1 and 680m5 on WinXP.
Comment 4 michael.ruess 2007-02-09 09:52:24 UTC
This is not a problem of the fact, that a master document is used. You can also
see the problem in the attached .odt when adding some rows to the table at the
end of the document.

The problem is, that the table is too complex, which means that cells have been
merged too often to calculate the break correctly. The problem is already
tracked as issue 43411

*** This issue has been marked as a duplicate of 43411 ***
Comment 5 michael.ruess 2007-02-09 09:57:56 UTC
Closing duplicate.