After the discussions in bug 80640 and bug 38262 regarding an outline view, a temporary fix is for navigator to be used with content view enabled. Unfortunately when you move entries in this view, when it refreshes, it collapse all other entries, so it would be good if it didnt do this.
Confirmed on LibreOffice 4.2.5 on OpenSuse.
isn't this bug 36308 - [UI]Change behaviour for "tree view" on Writer's Navigator or bug 42786 - Dragging Chapters with Navigator works wrong or bug 58186- EDITING: Navigator is not Updated, if a Chapter Move (in the navigator) is Undone in the document (with Undo) or bug 58187 - EDITING: Unintended Collapse of Headings in Navigator while moving a chapter or bug 58189 - EDITING: Wrong Chapter Moves with the Navigator or bug 58191 - EDITING: A “+” is Displayed Incorrectly at the Mouse Pointer while Moving a Chapter inside the Navigator: copying is not available, only moving or bug 58192 - EDITING: Enhancement: Open Text Document with Headings Expanded in Navigator or bug 63744 - Navigator view moves and closes hierarchy while typing in document or bug 65625 - EDITING: Navigator tree closes when reorganising headings ... Ah well, time for some solid analysis, clear mockups and a developer to rewokr the whole stuff, I guess ;)
Hey Cor, Well all of those bugs are related to Navigator not in content view mode, but it seems that even when its not in that content view mode, it doesnt retain the previous collapse behaviour.
This seems to have been fixed as it doesnt collapse for me in 4.4 daily or master. Version: 4.4.2.0.0+ Build ID: 4bc49565331c931f0efb3590db76267a5c911053 TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:libreoffice-4-4, Time: 2015-02-21_01:37:02 Version: 4.5.0.0.alpha0+ Build ID: 4cf69df2f543b023f4ec3d4279c5ac11a2a819d9 TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2015-02-21_03:46:34
** 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.5 or 5.1.2 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-04-16
** 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.2.7 or 5.3.3 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-20170522
ok in Versie: 5.4.0.3 Build ID: 7556cbc6811c9d992f4064ab9287069087d7f62c CPU-threads: 4; Besturingssysteem:Linux 4.10; UI-render: standaard; VCL: gtk2; Locale: nl-NL (nl_NL.UTF-8); Calc: group