Description: Format --> Paragraph --> Text Flow --> Keep with next paragraph toggle not working as expected. Paragraphs marked with Keep with next paragraph enabled are on previous page. Steps to Reproduce: 1. create a multi-page document 2. apply heading styles and body paragraph styles 3. manually toggle Keep with next paragraph Actual Results: if "next" paragraph is on the next page, sometimes when Keep with next paragraph is checked, it does not follow the "next" paragraph to the next page. Expected Results: If "keep with next paragraph" is checked and "next" paragraph is on the next page, bump the paragraph to the next page. Reproducible: Always User Profile Reset: No Additional Info: Version: 5.4.2.2 (x64) Build ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4 CPU threads: 4; OS: Windows 6.19; UI render: default; Locale: en-US (en_US); Calc: group User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
Created attachment 137360 [details] Example screen shot
Created attachment 137361 [details] Source document for the screen shot
I confirm this bug with the attached document and LO 5.4.2, but I remember the same behaviour in my own documents. If you open the paragraph dialog, disable and enable the "keep with next paragraph" option, it works. Version: 5.4.2.2 (x64) Build-ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4 CPU-Threads: 4; Betriebssystem:Windows 6.19; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group
** 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
still repro in Version: 6.2.0.0.alpha0+ Build ID: cec31fdedd7c94f4ebf903a66456a75867db22b0 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2018-10-21_22:54:44 Locale: ru-RU (ru_RU); Calc: threaded
Issue both for "fileopen" and "formatting" if resaved in LO. Similar fileopen for this DOC and DOCX if resaved in MSO. I can repro from 4.2 with the example at "7. Irish Amber Ale". I don't repro with 4.1. Let's try with bibisect.
Bibisected fileopen with Linux 42max commit 81de606c74699a98019c1dffccf6705af4bac21d Author: Matthew Francis <mjay.francis@gmail.com> Date: Sat Sep 5 22:14:46 2015 +0800 source-hash-ae88290f87acf693fed02140ca384ec15589616b Bibisect: This commit covers the following source commit(s) which failed to build d2eb26b4979b18c0cad0a57d9081e9f4c367f9f7 4db91c7db633b2e141d340bead677458f2d511a7 ea2738ec4571530ef2e40f1c9862a358df3dd08c 05ef22774ac842ffff96eeec3a3cdcfa3c292d2f 4de7cabd467c1ae3c94d2d32b867b5e7f956133d 9ecf5b47b9abb5e08eef3e1ff73267f0b5a74dff 8f0afc05f58630cabadcb67f6acc4998a7e7a258 99ba2fd24fcfc086353221d78ae64ffe159db3d6 c400d41b93421268d1b71f9b029285fc8a855ba0 da18612bf67b1f7caf9d94f4d8cb7fbd626e09f2 b009e8fd4fce06d9abae8aaac8750ece7df212e4 f852bda5ecf68c9450925bc95138509ffadb4a43 763114f8b7a7705e1b28226da33bf00016ad7982 8396cce9b5d9a4e3cdccc558eb1b818460f0987a e2d8e4716ae1276e750139d4e292c198f03228ec c4498251cb7181a9f272b0720f398597c0daef09 https://gerrit.libreoffice.org/plugins/gitiles/core/+log/d2eb26b4979b18c0cad0a57d9081e9f4c367f9f7..ae88290f87acf693fed02140ca384ec15589616b For some reason the range is not showing this https://gerrit.libreoffice.org/plugins/gitiles/core/+/d2eb26b4979b18c0cad0a57d9081e9f4c367f9f7%5E!/ I could not figure out what commit might be the cause.
Created attachment 148322 [details] Andrew's Recipe list_minimal.doc: reduced example (In reply to Buovjaga from comment #7) > I could not figure out what commit might be the cause. I eliminated parts of the document (starting with the TOC) and came up with a three page version that fails as far back as I can test in bibisect43all (so before LO3.6). Not a regression - just a change that triggered an existing bug.
repro 7.1+. The Comments-style paragraphs are NOT marked with keep-with-next, so each recipe ought to stick together on a full page. Likely this is somehow related to styles? The keep with next attribute is set on the Body style. The comment style INHERITS from the Body style - but turns off the keep-with-next attribute. Note that any change in the document that forces a layout change "fixes" the problem (for example, switching to web view and back).
Dear Andrew, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug