Description: Automatic page breaks are not applied across the whole heading1 style. Steps to Reproduce: 1. add 3 lines of "hello" 2. CTRL-1 them to heading 1 3. go to paragraph options, set "insert page break before", and apply 4. update style Actual Results: Applies only to the one item, not all heading1 Expected Results: Pagebreak should appear before all heading1 on "update style" Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
Seen on: Version: 5.2.7.2 Build ID: 1:5.2.7-1 CPU Threads: 2; OS Version: Linux 4.9; and: Version: 5.4.0.2 (x64) Build-ID: 2b906d450a44f2bbe506dcd22c51b3fa11dc65fd CPU-Threads: 4; Betriebssystem:Windows 6.1
Possibly related? https://bugs.documentfoundation.org/show_bug.cgi?id=103148
Works for me with LO 5.2.7.2 und LO 5.3.5.1 (Win 10 x64)
Repro from 4.2. to master. Update style is I guess available from Sidebar in 4.2, then button is available in Sidebar from 5.0. Later in 5.1. added in Style menu. Not related exclusively to heading, same with any style. Related to "insert page break before" which is not updated if single change in style, while updated if there's another change such as alignment. Similar behavior with New style from selection. So I change title from "Automatic page break not working for headings" to "Update style or New style not working for Insert page break before (except with other changes)" Not related to OS, so All. Note: adding a number of meta bugs that are blocked is in my view pointless and that time should be spent on testing and proper triaging of bugs; and in this case also not related to some Writer-Styles-Heading, whatever it is
So it seems page and column breaks before or after with or without page style info isnt being moved or copied to the styles. (In reply to Timur from comment #4) > Note: adding a number of meta bugs that are blocked is in my view pointless > and that time should be spent on testing and proper triaging of bugs; and in > this case also not related to some Writer-Styles-Heading, whatever it is It isnt pointless as many bugs touch more than one thing and the bug can be found in more than one location when it is relevant.
** 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
This bug does _not_ seem to be present any more in Version: 6.0.3.2 Build ID: 1:6.0.3-0ubuntu1 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: kde4; Locale: en-US (en_US.UTF-8); Calc: group @Timur: could you please confirm, and close if it works for you as well? Thanks!!
But still reproducible for me. Version: 6.2.0.0.alpha1+ Build ID: 0f190f50368816964b2a1b7bb58000ac1792d640 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); Calc: threaded from 2 days ago
Dear internationils, 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
Can confirm with these steps (a) add "Insert" page break (before or after) in Text Flow tab for a paragraph (b) Styles>Update Selected Style (or New Style from Selection) Actual result: the Insert is not updated in the paragraph's style and is not copied into a new style. Version: 6.5.0.0.alpha0+ (x64) Build ID: da70fd1edc211bf63f8388e11c1bd8dd398fdaf8 CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: default; VCL: win; Locale: en-US (en_DK); UI-Language: en-US Calc: threaded Additional information: Options (e.g., "keep with next paragraph) (also on the Text Flow tab) are updated and copied to a style).
Dear internationils, 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
Still present: Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded This bug is ancient, and I could imagine it affecting other style related updates as well... could someone please look at it?!?