In Writer it is not possible to hide the list of categories in the Navigator. Nothing happens when you click the "List Box On/Off." button. Harald Browser: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.23) Gecko/20110920 Firefox/3.6.23
Hi Harald, This only works when the Navigator is undocked - can you pls check that? For me it works fine. Thanks, Cor
Hi Cor, you are right. If the Navigator is undocked, the "List Box On/Off." button works fine. The problem is, that the "List Box On/Off" button is not greyed like other buttons in the Navigator, if they don't work. So I expected a reaction when I clicked it and nothing happens. Perhaps the button should be greyed, if the Navigator is docked. Regards Harald
thanks for confirming. Changing subject (was " UI: Button "List Box On/Off" in Navigator does not work " )
and confirming too ;-)
Hi Cor, try this: 1. Undock the Navigator. 2. Hide the list by clicking the "List Box On/Off" button. 3. Dock the Navigator again. In my system the list of categories is not displayed. The area where it should be is grey and it is not possible to display the list by clicking the "List Box On/Off" button. I think this behavior is not intended. Harald
Bug still exists in Version 3.6.3.
** 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.3.5 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) Thank you for your help! -- The LibreOffice QA Team
Problem still exists in 4.4.0.1
** 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.0.4 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: 2016-01-17
Bug still exists in version 5.0.4 with Win7.
** 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
Bug still exists in version 6.0.4 (64 bit, Win10).
Dear Harald Koester, 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
Hé, funny. Start Writer, Navigator being visible. > Button "List Box On/Off" is there Undock Navigator Dock it again > Button "List Box On/Off" is hidden. In 630 beta1 and 6.3 master. On Linux. @Harold: what about you?
(In reply to Cor Nouws from comment #14) > Hé, funny. > Start Writer, Navigator being visible. > > Button "List Box On/Off" is there > Undock Navigator > Dock it again > > Button "List Box On/Off" is hidden. > > In 630 beta1 and 6.3 master. On Linux. > > @Harold: what about you? The same with version 6.2.4 on Win10. I assume the intention was to display the button "List Box On/Off" when the Navigator is undocked and vice versa not display the button when the Navigator is docked. To my opinion this makes sense, but it does not work. Always if you open the Navigator docked with F5 or together with a new or existing document, the button is displayed and does not work. And a special effect that occurs if you switch the list box off: ... [1] Undock the Navigator. [2] Switch the list box off. [3] Dock the Navigator again. The List is not displayed and is replaced by a grey area. The "List Box On/Off" button is not displayed. Expected: List should be displayed. [4] Two times F5. Now the area is still grey and the "List Box On/Off" button is displayed, but it does not work.
Changing summary In 7.0.0.0.alpha, when Navigator is docked, no "List Box" icon is shown (as expected in comment 15 (so WFM) But comment 5 is still valid, that is: undock Navigator, turn off List Box, then dock Navigator -- no items are shown.
(In reply to sdc.blanco from comment #16) > Changing summary > > In 7.0.0.0.alpha, when Navigator is docked, no "List Box" icon is shown (as > expected in comment 15 (so WFM) For me, the content tool box "List Box" item is visible when the F5 Navigator is docked at Writer start. How about for you?
(In reply to Jim Raykowski from comment #17) > For me, the content tool box "List Box" item is visible when the F5 > Navigator is docked at Writer start. Confirmed. (have changed summary again.) Version: 7.0.0.0.alpha0+ (x64) Build ID: eeb2d19e77d6dc47c68e8ba0920a02cf64a1247b 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 To summarize the variations: 1. If Navigator is docked, and a NEW document is opened, then the docked Navigator shows a visible, inactive "List Box". 2. If Navigator is undocked and then redocked, the "List Box" disappears. (but opening a New document will still show a docked Navigator with an inactive "List Box") 3. If Navigator is undocked, and "List Box" is turned off, then redocking Navigator shows no items and no "List Box" (and no obvious way to show items again w/o undocking). (opening a New document now will also have a docked Navigator, now showing a "List Box" icon, but also showing no items)
Two bug fixes in one! https://gerrit.libreoffice.org/c/core/+/87758
Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/54b28638ab15f68731861ae903c732273b41f78a tdf#42695 Fix a couple Writer Navigator "List Box" related bugs It will be available in 7.0.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(In reply to Jim Raykowski from comment #19) > Two bug fixes in one! It is remarkable how sometimes a few lines of code can fix so much misbehavior. (In reply to sdc.blanco from comment #18) Feedback -- followed by dumb question. Main conclusion: the "problematic" parts are gone. > 1. If Navigator is docked, and a NEW document is opened, then the docked > Navigator shows a visible, inactive "List Box". No List Box shown in a New Document (with docked Navigator). > 2. If Navigator is undocked and then redocked, the "List Box" disappears. > (but opening a New document will still show a docked Navigator with an > inactive "List Box") List Box disappears (as before). No List Box in a New Document (with docked Navigator) > 3. If Navigator is undocked, and "List Box" is turned off, then redocking > Navigator shows no items and no "List Box" (and no obvious way to show > items again w/o undocking). Redocking shows all the categories. (but still no List Box) (do not know what should be expected. But probably would not expect all the Navigator categories to be shown in this case.) New/further tests: 1. When navigator is undocked, then opening a New Document also opens a Navigator in the same state as the document from which a New document was opened (i.e., if list box is closed, then new document has closed list box, if navigator content is shown, then new document shows navigator content, etc.) 2. Redocking Navigator (and opening a New document). It seems like the on/off state of "List Box" when Navigator is redocked has no effect when a New document is opened. In both cases (open or closed ListBox when docked), the New Document opens with a docked Navigator (and only shows one category). (could not completely get the "rule" for which category is shown. At first, it seemed to be the category where the cursor was located, but could not reproduce consistently). Dumb question: Why even keep the List Box in undocked Navigator? From a functional POV, it (sort of) duplicates "Content Navigation View". (I recognize that List Box turns off the Box where the Navigator items are shown, but turning off Content Navigation View (almost) does the same thing (except for the previous point where Content Navigation View continues to show at least one category when the Navigator is docked (or undocked).
Tests in comment 21 conducted with: Version: 7.0.0.0.alpha0+ (x64) Build ID: cf96cb11e2a46c452a273ded1c66c556118983cf CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; Locale: en-US (en_DK); UI-Language: en-US Calc: threaded
(In reply to sdc.blanco from comment #21) > Dumb question: Why even keep the List Box in undocked Navigator? I think this is a good question.