Created attachment 86890 [details] Outline Bug I've hit this bug so many times and could never figure out reproducible steps, now I can figure out two ways, they result in slightly different broken behavior but I think they are so related that I'm creating one bug report and one attachment to display the problem. Method 1: 1. Start outline (format -> Bullets and Numbering ...) 2. Select the 1st column, 2nd row style (I., I.A., i, a, bullet) 3. Push Ok 4. Type something next to first bullet "Test" is fine 5. Push enter 6. Tab as far to the right as you can (I believe 9 tabs) 7. Push the "increase indent" button which should be in your toolbar on top 8. Now try to decrease the level of the (either by the button in the outline toolbar "Promote One Level with Subpoints" or by holding Tab and pushing Backspace), do this several times, you'll see that despite the level changing (you'll see the change of the outline level for instance from a) to A) but the placement is all wrong) Method 2: 1. Start numbering style by pushing the button 2. Add some random text next to the number 1. "Test" is fine 3. Hold tab until it goes all the way to the right and "Test" or whatever goes to the next line on the far right 4. Place the cursor between the number 1. and your text 5. Push and hold tab, then start pushing backspace You'll see that the indent starts going back and it should but then it continues to go off the page, the margins are completely ignored, the page itself is completely ignored. Let me know if any of this isn't clear
Hi Joel, Can you pls explain what the use case of this actions is? thanks, Cor
Hey Cor, I'm not sure how much more I can explain, I just looked over the steps and they seem pretty straight forward :-/ As for use case, if you're asking why I'd want to do these things: Method I: The artificial limitation of 9 levels deep is not enough when doing complex outlines - so for me I get to the limit of 9 levels and then use the indent button to go 1 or 2 levels further. I don't get why we limit to 9 when that's only about half the page in Method II: Usually by accident this happens ;) But none the less, it triggers the bug
Joel, I can understand the issues, but they do not seem simple to me (or related) and the terminology can easily become confused. Method 1 is essentially about increasing the number of outline levels from 10 to something greater. My reading of ODF v1.2 Part 1 indicates there is no specified maximum number of outline levels, so it is likely an implementation limit. There are however several different types of outline, ignoring for a moment the heading vs list issue. Each time one of these lists is modified (e.g., before/after mark is changed, either via direct formatting or a style) a completely new set of N (currently 10) definition entries is created. In your sample file there are six such sets of (list) definitions. A second aspect to increasing the number of levels is that currently (on an A4 page) the existing 10 levels, using default settings, cover about half the page. This leaves half a page for the points to wrap in. Less than half a page for text to wrap in results in a fairly ugly layout. Cosmetic I know, but still a related consideration. I suppose 12 or 15 levels could be handy, but it may mean having to change the entire outline numbering for headings as well. Possibly a big change for a small inconvenience. Method 2 exhibits a problem with using TAB to manually set level. This can be demonstrated by clicking the Numbering On toolbar button, TAB, and then SHIFT+TAB repeatedly to force the list item into the left margin. The TAB method to change list levels certainly has issues and this one is probably covered (generally) by bug 49856. Note that this is all in relation to levels and not indents (Increase/Decrease toolbar buttons) which are separate matter again.
Oh, I forgot: Method 1 (increasing the number of levels) would also likely be an enhancement request, no?
Hi Owen - this has nothing to do with increasing the # of levels from 10 to more than 10. It's that even less than 10 results in incorrect placement.
@Owen - I just checked the attachment and the same problem shows - if you open the attachment, the bugs are pretty clearly seen
Joel, sorry, I mis-read Method 1 as relating primarily to the number of levels. There is certainly a problem with combining ordered lists using outline identification and indents, particularly with changing levels after an indent has been added. In this respect I can confirm the report. Status set to NEW. I re-tested Method 1 under Ubuntu 10.04 x86_64 running: - v3.3.0.4 OOO330m19 Build: 6 - v3.4.6.2 OOO340m1 Build: 602 - v3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b - v3.6.7.2 Build ID: e183d5b - v4.0.6.2 Build ID: 2e2573268451a50806fcd60ae2d9fe01dd0ce24 ... and the behaviour is identical for all versions. Problem appears to be inherited from OOo. Version set accordingly.
** 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 on a currently supported version of LibreOffice (4.4.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Version: 6.0.4.2 Build ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf CPU threads: 4; OS: Windows 6.1; UI render: default; Locale: en-US (en_US); Calc: CL Seems resolved. Closing