https://bugs.documentfoundation.org/show_bug.cgi?id=126704
Timur <ti...@libreoffice.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.documentfounda
| |tion.org/show_bug.cgi?id=14
| |4240
CC| |ti...@libreoffice.org
Resolution|DUPLICATE |FIXED
--- Comment #4 from Timur <ti...@libreoffice.org> ---
Sems wrong assumption... Fixed in 7.1 with:
commit 583ca42c3f83058aa6ccfff1063aef373d98e4c8 [log]
author Michael Stahl <michael.st...@allotropia.de> Fri Jun 25 10:25:59
2021 +0200
committer Thorsten Behrens <thorsten.behr...@allotropia.de> Mon Jun
28 09:40:54 2021 +0200
tree 844213d328ea14b8b7c70f72c45d2195c5b55270
parent 82ec493928ae35d224ffdc735fd8e427c390610c [diff]
sw: layout: fix table split loop caused by RemoveFollowFlowLinePending
In no_view.odt, the table 1340 does RemoveFollowFlowLine(), then splits
again, and by the time Split() returns, its flag
m_bRemoveFollowFlowLinePending is set and so in the next
SwTabFrame::MakeAll() it will do the same thing again, until eventually
it hits
layact.cxx:544: LoopControl_1 in SwLayAction::InternalAction
The flag is set during lcl_RecalcSplitLine(), in SwContentFrame::Cut(),
which operates under the assumption that there are no other cells in the
follow flow line that may contain content frames.
This only happens if "Verdana" and "Arial" fonts are available and not
substituted with "DejaVu Sans" etc.
--
You are receiving this mail because:
You are the assignee for the bug.
