Problem description: It is not possible to rearrange chapters of a document which is opened as read-only file with the Navigator under the following conditions: (1) a) Open the document, b) the Navigator is already visible (state of last session), c) click "Edit File" icon. (2) a) Open the document, b) the Navigator is hided (state of last session), c) click "Edit File" icon, d) "Show" Navigator. (3) a) Open the document, b) the Navigator is hided (state of last session), c) "Show" Navigator, c) click "Edit File" icon. (4) a) Open the document, b) the Navigator is closed (state of last session), c) open Navigator (F5), d) click "Edit File" icon. In these 4 cases the 4 icons in the right corner of the Navigator are grayed and can't be used. If you close the Navigator (F5) and open it again (F5) rearranging chapters is possible. Simple but you have to know. If you open the Navigator in case 4 after clicking the "Edit File" icon, rearranging of chapters is also possible. Regards Harald Browser: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.24) Gecko/20111103 Firefox/3.6.24
Rearranging chpaters is also possible if you click "Content View" in the Navigator. Also simple but you have to know.
Could you attach any example documents to allow others to check on different system/build?
Created attachment 64728 [details] Example file Just open the example document and follow the steps described inside.
Confirmed, it's not consistent and closing then reopening navigator changes the behavior. Setting as NEW, Prioritizing, Assigning to myself
With the latest alpha release I'm unable to reproduce this. The navigator is grayed out always (I tried closing and reopening several times) and it's always grayed out (which is what is expected for a read-only file). I'm going to mark as RESOLVED. If when the next release comes out you still see the problem please reopen it, apologies for the confusion. Version 3.7.0.0.alpha0+ (Build ID: 711958d)
Hi Joel, I again checked the bug with Master (4.0.0.0.alpha1+, 2012-11-26). The bug still exists. Could it be, that you forgot to click "Edit File". After clicking, the buttons are still greyed and it is not possible to rearrange the chapters.
marked as UNCONFIRMED until I get another chance to test out. Thanks for the update :)
Okay so definitely still verified - sorry for the long delay. So here it goes: Thank you for reporting this issue! I have been able to confirm the issue on: Version 3.6.6.2 & on Version: 4.1 master pulled Wed May 8 18:48:38 2013 +0200 Platform: Bodhi Linux 2.2 x64 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Marking as: New (confirmed) Minor - doesn't prevent high quality work, workaround is just to close and reopen navigator Low - only happens in very rare circumstances, in 17 months no additional dupes or comments from other people outside of triagers and OP Keywords - Whiteboard Status - ProposedEasyHack + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
Removing comma from whiteboard (please use a space to delimit values in this field) https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Whiteboard#Getting_Started
In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval. Thank you and apologies for the noise
Checked again with versions 4.3.5 and 4.4.0.2 (RC2). Bug still exists in both versions.
Migrating Whiteboard tags to Keywords: (needsDevEval) [NinjaEdit]
** 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.6 or 5.2.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-20170103
Bug still exists in version 5.3.0. (Win7) Bug already exists in version 3.3.0. Hence inherited from OOo.
** 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 with version 6.0.5 (64 bit, Win10).
https://gerrit.libreoffice.org/56985
Mike Kaganski committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=44c0d38a06cd5ab765facef3242e2c0e3e7944b4 tdf#43438: SwContentTree: handle ModeChanged notification It will be available in 6.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Checked with version 6.2.2. Works as expected now. Thanks for fixing.