Created attachment 180014 [details] Screenshot Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 0c87c0b87a3bbc2c57b2dd65ba2dd0aeb2f0b0c3 CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL Make the document window narrow enough that toolbars don't fit into the width; then click on the [>>] button that allows to see the rest of the toolbar's buttons (see the screenshot) The popup panel has 2-pixel top border (the rest have 1-pixel) on Windows 10; it starts a bit too high, so that the [>>] button itself covers 1-pixel part of the border. "Regression" after commit 81d4fbc0daa54889ccb09e6a3fadff9c70d99448 Author Maxim Monastirsky <momonasmon@gmail.com> Date Sun Feb 12 22:14:48 2017 +0200 tdf#42029 Use a floating toolbar to show clipped items Or rather, a small implementation error.
Created attachment 180023 [details] Screenshot detail I can see a two pixel border in four sides, but do not know why is lighter at the top left border. Maybe the Windows of the original post use same colors. Version: 7.1.8.1 (x86) / LibreOffice Community Build ID: e1f30c802c3269a1d052614453f260e49458c82c CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: es-MX (es_MX); UI: en-US Calc: threaded
Created attachment 180024 [details] Another screenshot detail This time the lighter color is at the top right border. I deduce that it is shown at the >> button nearer side. Maybe, not a bug.
No idea why the top border in that screenshot is wider, and can't remember seeing anything like this before. However it's expected for the top border to not be drawn underneath the button, so that the button and the popup look like a single continuous area. This was introduced for subtoolbar popups back in OOo for i#32185, and later expanded to other popups in Go-oo's toolbar-decorations-vcl.diff. The problem here is that the ">>" button doesn't show the pressed state when clicked, which is why it looks worse.
Dear Mike Kaganski, 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