Created attachment 114069 [details] Sidebar screenshot Inconsistent resizing behaviour in the sidebar. Steps to reproduce: 1. Open Libreoffice Writer and make sure the sidebar is enabled. 2. Try to reduce the size of the sidebar when the "Properties" tab is selected. 3. Try to reduce the size of the sidebar when the "Styles and Formatting", "Gallery" and "Navigator" tabs are selected. Current Behaviour: When the "Properties" tab in the sidebar is selected, the sidebar will only reduce in size to a certain point to allow all elements to be visible. When reducing the size of the sidebar when the other tabs are selected, the sidebar will reduce to nothing (there is no minimum size in these tabs). Expected Behaviour: The sidebar should either 1. Reduce only so much to allow all elements to be visible (as per the current "Properties" tab) or 2. Reduce freely as much as the user may want (even allowing a reduction in size to nothing). One thing to note is that if the user reduces the sidebar without limits, some elements may not be visible and the user may not be aware of them. I have attached a screenshot to illustrate the problem. Note that this inconsistency is present in Calc, Impress and Draw as well. Tested with the following setups: LibreOffice 4.2.7.2 from the Ubuntu 14.04 repo LibreOffice 4.4.1.2 from the Ubuntu 15.04 repo LibreOffice Version: 4.5.0.0.alpha0+ Build ID: 33434f47ac44f5cb4612a11b1c28c4582976cb25 TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-03-12_00:51:47 Locale: en_AU
Reproducible with LO 4.4.1.2, Win 8.1 I think it should show the behaviour as in 1. of the in the Bug Report mentioned Expected Behaviour, because normal LO dialogs can also not be closed to zero, because it also does not make sense.
** 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
This bug is still present in LibreOffice 5.1.2 on Ubuntu Gnome 16.04.
** 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
*** Bug 114148 has been marked as a duplicate of this bug. ***
In reply to comment 4: I confirm that this bug is still there in LibreOffice 5.4.3.2-1.fc27 on Linux Fedora 27.
** 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
This bug is still present in the latest LibreOffice 6.5 daily builds. Version: 6.5.0.0.alpha0+ Build ID: bb9c74189c9d8dd3e4de7efe94b9ba8d158a9133 CPU threads: 12; OS: Linux 5.3; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-01-12_22:58:52 Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded
I think the discussion about this is being done in bug 90374
Maybe the original issue has been fixed, otherwise it's by design. The sidebar should have an initial width defined by the largest deck. The deck's width itself is defined by the content on it, no control must be cropped. However, it should be possible to resize the decks so it might become smaller than initially (given the controls allows that).