Issue 17941 - large table cell causes problems in pagination
Summary: large table cell causes problems in pagination
Status: CLOSED DUPLICATE of issue 2109
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 1.1 RC2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: h.ilter
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2003-08-06 20:10 UTC by bikehead
Modified: 2003-09-08 16:56 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description bikehead 2003-08-06 20:10:41 UTC 
I have a two column table with one row.  Each cell has a large amount of text in
it (more than the page).  In non-outline view mode (I don't know that true name
for this) the table gets chopped off at the end of the page.  Scrolling past
this table results in many alarm beeps.

At one point I split both cells in the row multiple-times.  Again the amount of
text in all the cells was greater than the page.  At this point printing and
display of the table became unstable.  Some times OO chips the table, other
times it misaligns the table and overpints it on the paragraphs following the table
Comment 1 tamblyne 2003-08-06 20:42:00 UTC 
Please attach the document creating the problem to your report.  

Thanks,  

Tam
Comment 2 bulbul 2003-08-06 20:58:29 UTC 
The issue of a single table cell not being able to span multiple pages
is a duplicate of bug 2109, which is planned to be fixed in OOo 2.0.

As for the printing problem, this looks a lot like bug 13976.
Comment 3 rblackeagle 2003-08-07 04:30:09 UTC 
I keep puzzling over this one, but I think I know what's intended.  It
seems to me that a two-column page style and the use of connected
frames would be better suited to the intended usage than trying to put
so much text in a table cell.  Have you looked into that way of
solving the problem?
Comment 4 tamblyne 2003-08-28 05:38:17 UTC 
.

*** This issue has been marked as a duplicate of 2109 ***
Comment 5 tamblyne 2003-08-28 05:38:39 UTC 
.