Problem description: Selecting various numbers for "Heading Levels Shown" in the Navigator dialog control bar seems to have no effect on the numbers of header levels shown. Steps to reproduce: 1. Open a document with several levels of headers 2. Press f5. The Navigator dialog appears and shows the level 1 headers 3. Click the down arrow on the Heading Levels Shown drop down box and pick, say, 10. The number of levels displayed is unchanged. Current behavior: Clicking a number in the Heading Levels Shown drop down box seems to do nothing Expected behavior: Clicking a number in the Heading Levels Shown drop down box collapses or expands the header tree to show all levels of all branches up to and including the level number selected. Platform (if different from the browser): Fedora 16 using XFCE Browser: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20100101 Firefox/8.0
NOT Reproducible with "LibreOffice 3.4.4 - WIN7 Home Premium (64bit) German UI [Build ID: OOO340m1 (Build:402)]". Modifying in Navigator context menu 'Outline level' shows or hides exactly the expected headings in my sample document. @reporter: please attach a sample document and contribute a document related stp by step instruction!
I have the same situation with one difference: collapse is working, but expanding is not. LibreOffice 3.4.4. Platform : Fedora 16 using GNOME3, Cinnamon.
Created attachment 56043 [details] Test document
The behaviour of «Heading Levels Shown» depends on position in the document. It is not correct. Let's reproduce bug. Go to the first line in the document and then collapse list of headings in the navigator panel choosing 1 from «Heading Levels Shown». Then choose for example 5. Nothing expanded! But if we press Ctrl+End (go to the bottom of document) all levels appears.
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian