Issue 26945 - Word9: CellbreakingTable in Table with images does not break on next page
Summary: Word9: CellbreakingTable in Table with images does not break on next page
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1.1RC
Hardware: All Windows XP
: P3 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords:
: 31622 32695 (view as issue list)
Depends on: 2109 25676
Blocks: 35143
  Show dependency tree
 
Reported: 2004-03-24 19:45 UTC by bjfischer
Modified: 2013-08-07 14:41 UTC (History)
2 users (show)

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

Attachments
Word9 document with many images (378.00 KB, application/msword)
2004-03-24 19:47 UTC, bjfischer 		no flags Details
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 bjfischer 2004-03-24 19:45:37 UTC 
The attached Word9 document is not at all correctly displayed.

There are 21 pages in the document, OO says there are 4.

Everything is upside down.
Comment 1 bjfischer 2004-03-24 19:47:24 UTC 
Created attachment 14054 [details]
Word9 document with many images
Comment 2 michael.ruess 2004-03-25 09:12:43 UTC 
MRU->OD: This should be kept as reminder. The attached document can only be
displayed correctly in OO Writer when:
1. Ability of table cells to break on next page is implemented (has been done by
issue 2109)
2. Table in Table has been implemented (see issue 25676) in OO Writer
3. Enable page break capability of Table cells containing frames/graphics
Comment 3 Oliver-Rainer Wittmann 2004-03-26 11:10:40 UTC 
accepted.
Comment 4 Oliver-Rainer Wittmann 2004-04-28 10:35:16 UTC 
add dependencies
Comment 5 michael.ruess 2004-07-21 12:54:57 UTC 
*** Issue 31622 has been marked as a duplicate of this issue. ***
Comment 6 lohmaier 2004-08-06 20:54:05 UTC 
*** Issue 32695 has been marked as a duplicate of this issue. ***
Comment 7 Oliver-Rainer Wittmann 2004-10-18 09:07:50 UTC 
fixed in cws swqbugfixes09 - changed files:
/sw/inc/anchoredobject.hxx, 1.6.40.1
/sw/source/core/layout/anchoredobject.cxx, 1.6.40.1
/sw/source/core/inc/tabfrm.hxx, 1.12.144.1
/sw/source/core/layout/tabfrm.cxx, 1.67.38.1
/sw/source/core/objectpositioning/tocntntanchoredobjectposition.cxx, 1.8.40.1
/sw/source/core/text/txtfly.hxx, 1.8.416.1
/sw/source/core/text/txtfly.cxx, 1.49.40.1
/sw/source/core/inc/layouter.hxx, 1.2.108.1
/sw/source/core/layout/layouter.cxx, 1.6.72.1
/sw/source/core/inc/movedfwdfrmsbyobjpos.hxx, 1.2.108.1
/sw/source/coure/layout/movedfwdfrmsbyobjpos.cxx, 1.2.108.1
/sw/source/core/inc/anchoredobjectposition.hxx, 1.7.108.1
/sw/source/core/objectpositioning/anchoredobjectposition.cxx, 1.8.68.1
/sw/source/core/inc/objectformatter.hxx, 1.2.108.1
/sw/source/core/layout/objectformatter.cxx, 1.2.108.1
/sw/source/core/layout/objectformatterlayfrm.cxx, 1.2.108.1
/sw/source/core/layout/objectformattertxtfrm.hxx, 1.2.108.1
/sw/source/core/layout/objectformattertxtfrm.cxx, 1.3.40.1
/sw/source/core/layout/flowfrm.cxx, 1.42.108.1
/sw/source/core/layout/fly.cxx, 1.64.40.1
/sw/source/core/layout/flycnt.cxx, 1.43.40.1
/sw/source/core/layout/flylay.cxx, 1.37.108.1
/sw/source/core/layout/layact.cxx, 1.45.40.1
/sw/source/core/inc/frame.hxx, 1.41.72.1
/sw/source/core/frmedt/fews.cxx, 1.28.10.1
Comment 8 Oliver-Rainer Wittmann 2004-10-27 10:39:16 UTC 
additional correction needed at method <SwFlowFrm::IsPrevObjMove()> - change file:
/sw/source/core/layout/flowfrm.cxx, 1.42.108.2
Comment 9 Oliver-Rainer Wittmann 2004-11-05 12:03:08 UTC 
reopen to assign to QA
Comment 10 Oliver-Rainer Wittmann 2004-11-05 12:04:02 UTC 
OD->MRU: Checked in internal installation set of cws swqbugfixes09 - please verify.
Comment 11 Oliver-Rainer Wittmann 2004-11-05 12:04:29 UTC 
set status back to FIXED
Comment 12 michael.ruess 2004-11-11 10:39:58 UTC 
Verified fix in CWS swqbugfixes09.
Comment 13 michael.ruess 2005-04-04 09:46:10 UTC 
The document can be opened now. The document will not look correctly though. But
for a full fix of this, issue 25680 must also be fixed (will be done soon).