Description: Text Flow Break seems to be enabled by default when importing a doc containing a table Steps to Reproduce: 1. Open attachment 74823 [details] (bug 59770) 2. Right click the table -> Table properties -> Tab textflow 3. Text Flow Break is enabled. Actual Results: Text Flow break shouldn't be enabled. The table ends up on a new paste when copy/pasting it. Expected Results: Text Flow break should be disabled Reproducible: Always User Profile Reset: No Additional Info: Version: 5.4.0.0.alpha1+ Build ID: 8c0be54a7da6262dffe04357121814dd22b5d7fe CPU threads: 4; OS: Windows 6.2; UI render: default; TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2017-05-15_01:35:45 Locale: en-US (nl_NL); Calc: single User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Hi Telesto, Reproduced with LO 5.4.0.0.alpha1+ Build ID: 034be10413ed4915090678ad4f1d48596cf5e206 CPU threads: 2; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@39, Branch:master, Time: 2017-05-17_03:17:37 Locale: fr-FR (fr_FR); Calc: CL and also with LO 3.5.3.2 Version ID : 235ab8a-3802056-4a8fed3-2d66ea8-e241b80 so probably inherited from OOo.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Confirmed with LO 6.0.4.2 Build ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf Threads CPU : 2; OS : Windows 6.1; UI Render : par défaut; Locale : fr-FR (fr_FR); Calc: CL
It sounds like it came from here, but disabling that didn't solve the problem: // if first paragraph in table has break-before-page, transfer that setting to the table itself. else if( false && StyleExists(m_nCurrentColl) ) { const SwFormat* pStyleFormat = m_vColl[m_nCurrentColl].m_pFormat; if( pStyleFormat && pStyleFormat->GetBreak().GetBreak() == SvxBreak::PageBefore ) NewAttr( pStyleFormat->GetBreak() ); } In fact, I can't find where it is coming from, but it also happens with the first paragraph int a blank document in both doc and docx. So it might be a requirement to start a document in MS formats with a pagebreak.
Fixed in LO 7.1 beta by author Justin Luth on 2021-02-26 12:24:17 +0100 commit 1c8df3e58940bf6abdbda0b2f932a5990b577fae tdf#118711 doc import: don't hardcode default page description well, at least not at the beginning of the document. This is a .DOC followup to the 7.1 .DOCX patch in commit 8787a45f9cbb5dce61b20817ef0e549b5a227a95. *** This bug has been marked as a duplicate of bug 118711 ***