<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - DOC LAYOUT specified height row splits and flows back to previous page, despite not meeting minimum height (comment 9)."
href="https://bugs.documentfoundation.org/show_bug.cgi?id=105478#c17">Comment # 17</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - DOC LAYOUT specified height row splits and flows back to previous page, despite not meeting minimum height (comment 9)."
href="https://bugs.documentfoundation.org/show_bug.cgi?id=105478">bug 105478</a>
from <span class="vcard"><a class="email" href="mailto:jluth@mail.com" title="Justin L <jluth@mail.com>"> <span class="fn">Justin L</span></a>
</span></b>
<pre>So it is interesting that if the content is LESS THAN the minimum height, then
LO already doesn't try to split the row. However, if the content is MORE THAN
the minimum height, then it will split the row at any point.
I think this phenomenon is described by:
<span class="quote">> 3. It turns out, that if contents of the splitted cell has less
> height than the min height setting, then following happens.
> In SwTabFrame::Split, all rows below splitted one are moved to
> follow flow table; then table frame's Shrink method used to shrink
> the freed height. At this moment, still, the height of splitted
> row is too high, and total height of table is too high. Then,
> lcl_RecalcSplitLine is called, where row is first shrunk, and then
> lcl_RecalcRow and SwRowFrame::Calc try to move contents and resize
> the splitted row. They get the minimum height of content (we already
> don't consider the min height setting), but then "last row will fill
> the space in its upper" (see SwRowFrame::Format). Row returns its
> previous size, table does not resize, it doesn't fit to page, and
> split fails.</span >
Proposed patch (for just MS formats) is at
<a href="https://gerrit.libreoffice.org/c/core/+/93414">https://gerrit.libreoffice.org/c/core/+/93414</a>
For MS Word documents, the answer is obviously to follow MS layout, and not to
split unless the minimum size fits. But considering this mild discrepancy,
should we make the same change to ODT - in order to be interoperable at design
time with MS? After all, it acted this way until LO 5.3.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>