Created attachment 100158 [details] Bottom Toolbar Separator in 3.6 (top) and 4.3 beta (bottom) When a toolbar shows up at the bottom, like the table toolbar in writer, the black separator has moved to the bottom in 4.0 and above. Tested on Linux. In Windows 7 there are no toolbar row separators.
Created attachment 100159 [details] how the toolbar looks in windows 7
Separators are really needed in windows 7.
I see the separator at the top and bottom were there in 3.6 in Windows. :)
There are no borders in 4.1, 4.2 and 4.3 LibreOffice versions. Look at the file "Default UI" to see the actual UI. Look at the file "Mockup UI" to see what is the option proposed. (could be in Tools > Options... > LibreOffice > View ?)
Created attachment 100175 [details] Default UI (4.2)
Created attachment 100176 [details] Mockup UI (4.2)
Created attachment 100177 [details] Default UI (4.2) CORRECT Sorry, the previous version was 4.1, this is the correct "Default UI"
I'm running Linux Mint 13 Mate.
I'm running openSUSE 13.1 KDE.
Just to be clear, a separator is appearing with the bottom toolbar, but its appearing at its bottom, right above the top separator for the statusbar. So i'd like the separtor moved back to the top, similar to 3.6.
Created attachment 100759 [details] LibO 3.6 VS 4.0 with Mint-X theming
** 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.4.1 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: 2015-07-18
Issue is still present. Tested on Linux Mint 17.1 XFCE. Version: 5.1.0.0.alpha1+ Build ID: 5a2d6bf3a94f127307d6a9464033b2226508ff38 TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2015-08-21_06:31:09 Locale: en-US (en_US.UTF-8)
Migrating Whiteboard tags to Keywords: (bibisectRequest) [NinjaEdit]
I don't see this as a candidate for bibisectRequest - there's no evidence that this is a regression. Toolbars were moved to the bottom - with that came the changed border. There's never a time when it was on the bottom and the border was the way you propose. Removing bibisectRequest - if a developer thinks it would be useful feel free to add it again and let me know what behavior we're comparing....would it just be a bibisect to determine when the toolbar was moved to the bottom? Is there a time when it was on the bottom and the border was on top? I'd suggest even removing the "regression" keyword but I'll leave that to others to decide.
Adding keyword 'bibisectRequest'.
Xisco, Aron, Raal: can any of you guys bibisect this issue, as it still affects me today.
Sorry, it looks the same for me in the oldest and latest commit in Linux 43all repo (without a dark top border). Ubuntu 14.04.
Dear Yousuf Philips (jay) (retired), 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
(In reply to Buovjaga from comment #18) > Sorry, it looks the same for me in the oldest and latest commit in Linux > 43all repo (without a dark top border). Ubuntu 14.04. Now I realised I should use SAL_USE_VCLPLUGIN=gen while bibisecting and I was able to do it. I got the range https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=bed0447cefb949fc77cfde7543397d96590082ba..a581d31b227623e09d2970a91214fda398f98eda&ofs=50 and this definitely stands out alongside other related ones: https://cgit.freedesktop.org/libreoffice/core/commit/?id=e280b01cafdfd5c7c3b5660a8e9031a9eeb2865c Draw separating line at the top of the status bar. Adding Cc: to Jan Holesovsky
Dear Yousuf Philips (jay) (retired), 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug