Issue 81625 - Column break in table ignored
Summary: Column break in table ignored
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 2.2.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2007-09-17 00:52 UTC by eponymous
Modified: 2013-09-13 00:43 UTC (History)
2 users (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description eponymous 2007-09-17 00:52:52 UTC
Create a document with two columns (or create a section with two columns).
Create a table within that document, with two rows and two columns.
In the second row of the table, create a manual break > column break.

Nothing happens.

Expected behavior should be that the second table row moves into the second column.
Comment 1 eric.bachard 2007-09-17 06:13:32 UTC
Comment 2 michael.ruess 2007-09-17 09:15:17 UTC
Writer's tables are not designed to have a manual break applied to a special
row. But:
The whole table should move to the next column / page when a manual break is
applied. This works fine on Windows and Unix (tested with OO 2.2.1 and 2.3). The
fact that "nothing happens" in this case seems to be a Mac-only problem.
Comment 3 eponymous 2007-09-17 14:20:34 UTC
I don't understand the expected behavior described by mru.

What is a user supposed to do who desires to have a table break across a column at a particular row? Use 
multiple tables?

It's easy to imagine a scenario that would require such a break.
Comment 4 philipp.lohmann 2008-10-08 15:19:05 UTC
this does not seem to be mac specific at all, more a general writer issue
Comment 5 philipp.lohmann 2008-10-08 16:25:54 UTC
Comment 6 Mathias_Bauer 2008-11-05 10:19:27 UTC
If someone can confirm this it should go to fme.
Comment 7 michael.ruess 2008-11-05 16:45:05 UTC
A table should break when a page or column break is applied in  certain row.
This is what the user expects in this moment.
Currently this is not implemented in Writer's tables so this should be handled
as new "Feature".
Comment 8 eponymous 2013-09-13 00:43:53 UTC
How is the absence of an expected behavior not a bug, but a missing feature?

It does not behave as expected or in a reasonable way, so it's a bug.