Description: See my appended screen cast. I just created a second level header via "Ctrl + 2" after a bulleted list, and moved one item up. Steps to Reproduce: See above. Actual Results: Subsequent header gets moved. Expected Results: Subsequent header shouldn’t get moved. Reproducible: Always User Profile Reset: No Additional Info: It does not happen every time, seems to happen due to how the subsequent header is created. In my example I pressed "enter" two times at the end of the second bullet item, so that I exited the bulleted list. Then I entered the text and pressed "Ctrl + 2". User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Created attachment 137928 [details] Screen cast
I confirm it with Version: 6.0.0.0.alpha1 (x64) Build ID: c1d1f859b268f650143d48f294999cda0fa57350 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: de-DE (de_DE); Calc: group It seems to me like the second header is treatened like a subpoint.
*** Bug 114888 has been marked as a duplicate of this bug. ***
STR 1. Open attachment 138944 [details] (bug 114888) 2. Move “bla” (with sub-entries) up. Also found in Versie: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 Locale: nl_NL
Also in LibreOffice 3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5
** 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 not fixed in 6.1.4.2
WORKSFORME in Version: 7.0.4.2 (x64) Build ID: dcf040e67528d9187c66b2379df5ea4407429775 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL
repro 7.2+ I used the document and steps to reproduce from comment 4. When I move "bla" up with subpoints, "Heading" follows along with them. (This makes some sense. "Bla" is at listLevel 1, while "Heading" is a Heading 2, which is listLevel 2.) So, what SHOULD happen here? Should we ONLY move items up and down through the same numbering rule? But currently we can even move through normal paragraphs, so that would be a huge change. Our current method is very non-complex and therefore flexible - any list grouping can move up one "paragraph" regardless of the content. But I suppose it wouldn't be too hard to add an "if belongs to the same numbering rule" when deciding whether to include a line as a sub-point or not. [The problem with doing this is that it is VERY dependent on styles, while most people just use the toolbar, and might intentionally mix and match bullets/numbering to make sub-points.] If lcl_GotoNextPrevNum from docnum.cxx compares - if( pRule ) + if( pRule && pRule->IsAutoRule() == pOrigRule->IsAutoRule()) then I get the requested result. But that looks like a rather scary change that wouldn't just necessarily affect moving with subpoints. (Nor is "autoRule" documented, so I don't know exactly what that really is.)
->IsOutlineRule() is probably a better test in this situation. And yet, ultimately there should be nothing special about an OUTLINE_RULE verses a NUM_RULE. So I don't think it is safe to make any changes here, unless you are VERY clear about which points belong together.
*** Bug 123148 has been marked as a duplicate of this bug. ***
Please note that the duplicate issue in comment 11 is actually a different use case. However, I expect that a patch for one would solve the other also, but please make sure and test that workflow as well. repro 7.6+ using the documents and steps in comment 4.
Dear Frank Brütting, 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