https://bugs.documentfoundation.org/show_bug.cgi?id=103975
--- Comment #4 from Justin L <[email protected]> ---
Created attachment 128999
--> https://bugs.documentfoundation.org/attachment.cgi?id=128999&action=edit
tdf103975_notPageBreak.docx: reduced test document showing the problem
So far, my conclusion is that this has uncovered another bug, related to the
fact that these columns have no content. Adding a single character in one of
the columns prevents the problem. So does removing the HardReturn in the first
column. So clearly this is actually in column mode (visually confirmed in the
tab bar) even though FindColFrame() finds nothing (section attributes
GetCol().GetNumCols() also report 0).
Also - I failed to be able to create a clean-room test document in MSWord to
replicate the problem. This minimal unit test is just a reduced version of the
original.
The worst case fix for this particular document is to avoid it by:
const bool bPotentiallyHasColumns = m_rThis.FindColFrame() ||
m_rThis.IsInSct();
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
