Issue 62805 - A vertically merged cell splits the table unexpected place
Summary: A vertically merged cell splits the table unexpected place
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: OOo 2.0.1
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-06 09:41 UTC by raindrops
Modified: 2013-08-07 14:38 UTC (History)
2 users (show)

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


Attachments
Problem is illustrated (9.49 KB, application/vnd.oasis.opendocument.text)
2006-03-06 11:57 UTC, raindrops
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description raindrops 2006-03-06 09:41:38 UTC
It is not possible to split a table if the current row has a cell that is merged
with the row above.

1. Create a 4x8 table.
2. Merge the cells A4:A7.
3. Place the cursor in B4.1.2 (Erstwhile B5).
4. Select menu command Table > Split table.
The table is split, but the merged cells are kept together.

In other words, the command is not able to split the table at the desired point.
The entire group of row#5-8 is taken in the second table. 

When the table contains text, a split at the wrong place is not acceptable. So
the user would have to manually create extra rows in the second half and then
move the text from the first half. This means a lot of extra work for the user.

Desired: The table should split at the desired row. If there are any cells that
are merged with the rows above the current row, then they should be split
automatically. (If the merged cell contains text, it may be taken in the upper
half after splitting.)
Comment 1 raindrops 2006-03-06 11:57:54 UTC
Created attachment 34602 [details]
Problem is illustrated
Comment 2 michael.ruess 2006-03-06 13:25:37 UTC
MRU->FME: this issue is somehow located right in the middle between
"enhancement" and "defect". It is true, that the current "split table" behaviour
is conform with Writer's table concept. But on the other it is very confusing to
the user, that the table will be split at the top of the largest cell in the
merged part.
For the future an algorithm to detect such a situation and split the larger cell
in the desired/expected position automatically before the table becomes split is
needed.