Issue 65927 - optimal column width destroys layout of complex table
Summary: optimal column width destroys layout of complex table
Status: CLOSED DUPLICATE of issue 64391
Alias: None
Product: Writer
Classification: Application
Component: formatting (show other issues)
Version: OOo 2.0.2
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: frank.meies
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks: 72764
  Show dependency tree
 
Reported: 2006-05-30 19:04 UTC by skelem
Modified: 2013-08-07 14:44 UTC (History)
2 users (show)

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

Attachments
table whose columns get really messed up when resizing other columns (9.86 KB, application/vnd.oasis.opendocument.text)
2006-05-30 19:05 UTC, skelem 		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 skelem 2006-05-30 19:04:45 UTC 
Attached is a table that looks okay.  However...
1. Select the text "SSS Intercontinental Broadcast" in the lower left corner of
the table.
2. Click on Table/Autofit/Column Width.  The left column resizes okay.  However,
the columns labeled "PAPA", "MAMA", and "BABY" are resized in a way that
violates the previous column definition!
3. Click in the cell containing "A".
4. Resize the rightmost border of that cell, dragging it left to line up with
the line between "PAPA" and "MAMA".  When you let go, the cell containing "A" is
not resized!  Worse, the cell containing "RAM" has now stretched to include the
rightmost column!!!
Comment 1 skelem 2006-05-30 19:05:50 UTC 
Created attachment 36812 [details]
table whose columns get really messed up when resizing other columns
Comment 2 michael.ruess 2006-05-31 15:46:10 UTC 
MRU->FME: when performing a an "optimal column width" on a complex table like
the attached, some cell width are affected in an incorrect manner.  
This issue is VERY similar to issue  Issue 55794. Could please have a look if
this is a duplicate or really just similar? Thanks a lot.
We should really take a nearer target in mind than "later".
Comment 3 frank.meies 2006-06-26 07:11:23 UTC 
.
Comment 4 frank.meies 2007-12-04 07:46:25 UTC 
.
Comment 5 jian.li 2008-04-03 03:16:03 UTC 
lijian->fme:
I found that this issue was a duplicate of issue 64391. With 64391's patch, this
issue can be fixed. Please check this.
Comment 6 frank.meies 2008-04-03 07:11:42 UTC 
Yes, looks ok in current DEV300m4. I'll resolve this issue as duplicate.

*** This issue has been marked as a duplicate of 64391 ***
Comment 7 frank.meies 2008-04-03 07:12:10 UTC 
.